Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: pierre-marc.fournier@polymtl.ca (Pierre-Marc Fournier)
Subject: [ltt-dev] UST use case: Tracing QEMU/KVM
Date: Sun, 23 May 2010 23:57:33 -0400	[thread overview]
Message-ID: <1274673453.6759.5.camel@Nokia-N900-42-11> (raw)
In-Reply-To: <AANLkTinNkofN7tLVGtFXUo1oXNKGI6By6FPlS23BKny9@mail.gmail.com>

Hi Stefan,

Thanks for the feedback! A few comments:

----- Original message -----
> Here is feedback from adding UST tracing to QEMU/KVM.? Hopefully this
> will be useful to developers and maybe I can learn a more about LTTng
> UST from discussing hurdles I encountered.
>
> The architecture of UST looks good: pure userspace tracing support,
> tracepoints can be enumerated, enabled, and disabled at runtime.? The
> manual at http://lttng.org/files/ust/manual/ust.html is a nice
> quickstart although I suspect it only scratches the surface.

If there are specific subjects in mind you feel would benefit from being covered in more depth in the manual, please let me know.

>
> One note about the manual: the TP_PROTO() versus TPPROTO() change was
> confusing.? Perhaps a note can be added to the manual that ust.git
> uses TP_PROTO() but libust 0.4 uses TPPROTO()?

This reflects an API change in the kernel. But you are right, this is confusing. I will do a 0.5 release next week, which will obsolete 0.4 and sync the manual.

>
> When running the instrumented binary, the listener thread outputs
> noisy error messages:
> libust[28133/28134]: Error: poll: Interrupted system call (in
> multipoll_poll() at ../libustcomm/multipoll.c:84)
> libust[28133/28134]: Error: error in multipoll_poll (in
> listener_main() at tracectl.c:1015)
>
> Strace shows:
> poll([{fd=3, events=POLLIN}], 1, -1)? ? ? = ? ERESTART_RESTARTBLOCK (To
> be restarted)
> restart_syscall(<... resuming interrupted call ...>) = ?
> ERESTART_RESTARTBLOCK (To be restarted)

Hmmm. Do you have any pointers to documentation about this return code? I suspect userspace should never see it. Could it be a kernel bug?

>
> Finally, I had to add #undefs to get QEMU to build after including UST
> headers.? Unfortunately the UST headers include headers that pollute
> the (macro) namespace.
>

From examining the patch, I expect you are referring to mutex_lock and _unlock. I just did a commit to fix this.

> Any thoughts on these issues?
>
> My patch enabling UST sent to the QEMU mailing list:
> http://www.mail-archive.com/kvm at vger.kernel.org/msg34830.html

Thanks!

Pierre-Marc



  reply	other threads:[~2010-05-24  3:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-23 19:54 Stefan Hajnoczi
2010-05-24  3:57 ` Pierre-Marc Fournier [this message]
2010-05-24  9:00   ` Stefan Hajnoczi
2010-05-26 22:46     ` Pierre-Marc Fournier
2010-05-27  5:21       ` Stefan Hajnoczi
2010-05-27 19:36         ` Pierre-Marc Fournier
2010-05-27 20:22           ` Stefan Hajnoczi
2010-05-27 20:26             ` Mathieu Desnoyers
2010-05-24  8:41 Stefan Hajnoczi
2010-05-27 16:08 ` Pierre-Marc Fournier

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=1274673453.6759.5.camel@Nokia-N900-42-11 \
    --to=pierre-marc.fournier@polymtl.ca \
    /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