qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: [Qemu-devel] Re: [RFC 0/5] Tracing backends
Date: Sun, 23 May 2010 17:48:10 +0200	[thread overview]
Message-ID: <4BF94E3A.7010603@web.de> (raw)
In-Reply-To: <1274562503-10713-1-git-send-email-stefanha@linux.vnet.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

Stefan Hajnoczi wrote:
> The following patches against qemu.git allow static trace events to be declared
> in QEMU.  Trace events use a lightweight syntax and are independent of the
> backend tracing system (e.g. LTTng UST).
> 
> Supported backends are:
>  * my trivial tracer ("simple")
>  * LTTng Userspace Tracer ("ust")
>  * no tracer ("nop", the default)
> 
> The ./configure option to choose a backend is --trace-backend=.
> 
> Main point of this patchset: adding new trace events is easy and we can switch
> between backends without modifying the code.
> 
> Prerna: Would you like to add your tracing system as a backend?  This would be
> similar to my patches to add "simple" and "ust" backend support.
> 
> Jan: Adding kernel marker backend support should be straightforward if you are
> interested.
> 
> These patches are also available at:
> http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/tracing
> 

Nice! Will have a closer look once timer permits, specifically to check
how ftrace can be added to this. Looks indeed straightforward on first
sight.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      parent reply	other threads:[~2010-05-23 15:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22 21:08 [Qemu-devel] [RFC 0/5] Tracing backends Stefan Hajnoczi
2010-05-22 21:08 ` [Qemu-devel] [PATCH 1/5] trace: Add trace-events file for declaring trace events Stefan Hajnoczi
2010-05-24 22:07   ` Anthony Liguori
2010-05-25  9:11     ` Avi Kivity
2010-05-24 22:20   ` Anthony Liguori
2010-05-25  8:22     ` Stefan Hajnoczi
2010-05-22 21:08 ` [Qemu-devel] [PATCH 2/5] trace: Add simple built-in tracing backend Stefan Hajnoczi
2010-05-22 21:08 ` [Qemu-devel] [PATCH 3/5] trace: Add LTTng Userspace Tracer backend Stefan Hajnoczi
2010-05-23 15:50   ` [Qemu-devel] " Jan Kiszka
2010-05-22 21:08 ` [Qemu-devel] [PATCH 4/5] trace: Trace qemu_malloc() and qemu_vmalloc() Stefan Hajnoczi
2010-05-22 21:08 ` [Qemu-devel] [PATCH 5/5] trace: Trace virtio-blk, multiwrite, and paio_submit Stefan Hajnoczi
2010-05-23 15:48 ` Jan Kiszka [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=4BF94E3A.7010603@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=prerna@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).