public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Rayson Ho <rho@redhat.com>
To: kvm@vger.kernel.org
Subject: Tracing KVM with Systemtap
Date: Wed, 08 Sep 2010 09:20:30 -0400	[thread overview]
Message-ID: <1283952030.2631.19.camel@computer> (raw)

Hi all,

I am a developer of Systemtap. I am looking into tracing KVM (the kernel
part and QEMU) and also the KVM guests with Systemtap. I googled and
found references to Xenprobes and xdt+dtrace, and I was wondering if
someone is working on the dynamic tracing interface for KVM?

I've read the KVM kernel code and I think some expensive operations
(things that need to be trapped back to the host kernel - eg. loading of
control registers on x86/x64) can be interesting spots for adding an SDT
(static marker), and I/O operations performed for the guests can be
useful information to collect.

I know that KVM guests run like a userspace process and thus techniques
for tracing Xen might be overkilled, and also gdb can be used to trace
KVM guests. However, are that anything special I need to be aware of
before I go further into the development of the Systemtap KVM probes?

(Opinions / Suggestions / Criticisms welcome!)

Thanks,
Rayson




             reply	other threads:[~2010-09-08 13:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 13:20 Rayson Ho [this message]
2010-09-08 14:08 ` Tracing KVM with Systemtap Stefan Hajnoczi
2010-09-20 13:19   ` Rayson Ho
2010-09-20 13:36     ` Stefan Hajnoczi
2010-09-21 12:58       ` Rayson Ho
2010-09-21 13:33         ` Stefan Hajnoczi
2010-09-22 12:11           ` Rayson Ho
2010-09-22 12:33             ` Stefan Hajnoczi
2010-09-22 12:42               ` Rayson Ho
2010-09-22 13:39                 ` Stefan Hajnoczi

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=1283952030.2631.19.camel@computer \
    --to=rho@redhat.com \
    --cc=kvm@vger.kernel.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