From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
Avi Kivity <avi@redhat.com>
Subject: Re: [PATCH] Re: Tracing backends : Fix for building with --prefix
Date: Tue, 15 Jun 2010 14:49:54 +0100 [thread overview]
Message-ID: <20100615134953.GA20455@stefan-thinkpad.transitives.com> (raw)
In-Reply-To: <20100608120408.77258567@zephyr>
Thanks, applied! Got back from holiday today and am catching up on
tracing emails.
http://repo.or.cz/w/qemu/stefanha.git/commitdiff/3e59a5f51675d377a0fda88d4b83138a6b872962
Stefan
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: [PATCH] Re: Tracing backends : Fix for building with --prefix
Date: Tue, 15 Jun 2010 14:49:54 +0100 [thread overview]
Message-ID: <20100615134953.GA20455@stefan-thinkpad.transitives.com> (raw)
In-Reply-To: <20100608120408.77258567@zephyr>
Thanks, applied! Got back from holiday today and am catching up on
tracing emails.
http://repo.or.cz/w/qemu/stefanha.git/commitdiff/3e59a5f51675d377a0fda88d4b83138a6b872962
Stefan
next prev parent reply other threads:[~2010-06-15 13:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-25 10:24 [PATCH v2 0/7] Tracing backends Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [PATCH 1/7] trace: Add trace-events file for declaring trace events Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-06-08 6:34 ` [PATCH] Re: Tracing backends : Fix for building with --prefix Prerna Saxena
2010-06-08 6:34 ` [Qemu-devel] " Prerna Saxena
2010-06-15 13:49 ` Stefan Hajnoczi [this message]
2010-06-15 13:49 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [PATCH 2/7] trace: Support disabled events in trace-events Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [PATCH 3/7] trace: Add simple built-in tracing backend Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [PATCH 4/7] trace: Add LTTng Userspace Tracer backend Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [PATCH 5/7] trace: Trace qemu_malloc() and qemu_vmalloc() Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [PATCH 6/7] trace: Trace virtio-blk, multiwrite, and paio_submit Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 10:24 ` [PATCH 7/7] trace: Trace virtqueue operations Stefan Hajnoczi
2010-05-25 10:24 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 12:04 ` Avi Kivity
2010-05-25 12:04 ` [Qemu-devel] " Avi Kivity
2010-05-25 13:27 ` Stefan Hajnoczi
2010-05-25 13:27 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-25 13:52 ` Avi Kivity
2010-05-25 13:52 ` [Qemu-devel] " Avi Kivity
2010-05-25 14:00 ` Stefan Hajnoczi
2010-05-25 14:00 ` [Qemu-devel] " 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=20100615134953.GA20455@stefan-thinkpad.transitives.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=prerna@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.