From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] [UST] BUG Ubuntu <= Karmic
Date: Thu, 16 Sep 2010 20:57:56 -0400 [thread overview]
Message-ID: <20100917005756.GA14993@Krystal> (raw)
In-Reply-To: <4C92A11F.6070505@polymtl.ca>
* David Goulet (david.goulet at polymtl.ca) wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> After some talks in the metro and testing it here at home, we found the bad guy
> in all this mess... it is .... KVM :D
Ah, yes. This is why we need a strategy for a userland trace clock that
takes into account:
- The host kernel
- The guest kernel
- Userspace
Which is transparently available across all three.
Mathieu
>
> We have no idea yet why but we will look into it.
>
> Side note to my self : Test on different real host ;)
>
> Thanks
> David
>
> On 10-09-16 05:59 PM, David Goulet wrote:
> > Hi everyone,
> >
> > A very _major_ bug, to say the least, was discover this afternoon in
> > Ubuntu Karmic and below. The clock_gettime and gettimeofday function are
> > syscalls and not VDSO as it suppose to be.
> >
> > This makes UST go impressively slower because at each tracing event, you
> > got a syscall in the fast path. We got at 2 times factor (per event
> > speed) on Karmic and 5 times on Hardy.
> >
> > We are currently waiting for feedback from Debian and Ubuntu to explain
> > this changes in the glibc API. (If anybody knows why, please feel free
> > to explain it on this list).
> >
> > Here is a simple test to see if clock_gettime is in fact a syscall on
> > your distribution (we've only tested Ubuntu distro) :
> >
> > $ vim test.c
> >
> > #include <sys/time.h>
> > #include <time.h>
> >
> > int main(int argc, char **argv) {
> > struct timespec ts;
> > clock_gettime(CLOCK_MONOTONIC, &ts);
> > return 0;
> > }
> >
> > $ gcc -lrt test.c -o test
> > $ strace ./test
> >
> > If you see this line in the strace output :
> > clock_gettime(CLOCK_MONOTONIC, ...)
> >
> > it's a problem.
> >
> > Thanks to all
>
> - --
> David Goulet
> LTTng project, DORSAL Lab.
>
> 1024D/16BD8563
> BE3C 672B 9331 9796 291A 14C6 4AF7 C14B 16BD 8563
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
>
> iEYEARECAAYFAkySoR8ACgkQSvfBSxa9hWPSlwCeJpzliMvkiJ/26rCqF7SjJouv
> bD4AoIvUCOX+Jqfq/q12lvrPaDrptwV1
> =Hwbq
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
prev parent reply other threads:[~2010-09-17 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 21:59 David Goulet
2010-09-16 22:58 ` David Goulet
2010-09-17 0:57 ` Mathieu Desnoyers [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100917005756.GA14993@Krystal \
--to=compudj@krystal.dyndns.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox