From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Prerna Saxena <prerna@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/2] trace: Add simple tracing support
Date: Fri, 21 May 2010 23:41:49 +0200 [thread overview]
Message-ID: <4BF6FE1D.9020804@web.de> (raw)
In-Reply-To: <4BF6F5DF.2060703@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
Anthony Liguori wrote:
> I'm not opposed to using a framework, but I'd rather have an equivalent
> to kvm_stat tomorrow than wait 3 years for LTTng to not get merged.
>
> So let's have a dirt-simple tracing mechanism and focus on adding useful
> trace points. Then when we have a framework we can use, we can just
> convert the tracepoints to the new framework.
That could mean serializing the tracepoints to strings and dumping them
to our log file - no concerns.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] trace: Add simple tracing support
Date: Fri, 21 May 2010 23:41:49 +0200 [thread overview]
Message-ID: <4BF6FE1D.9020804@web.de> (raw)
In-Reply-To: <4BF6F5DF.2060703@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
Anthony Liguori wrote:
> I'm not opposed to using a framework, but I'd rather have an equivalent
> to kvm_stat tomorrow than wait 3 years for LTTng to not get merged.
>
> So let's have a dirt-simple tracing mechanism and focus on adding useful
> trace points. Then when we have a framework we can use, we can just
> convert the tracepoints to the new framework.
That could mean serializing the tracepoints to strings and dumping them
to our log file - no concerns.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-05-21 21:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:42 [RFC 0/2] Tracing Stefan Hajnoczi
2010-05-21 9:42 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-21 9:42 ` [PATCH 1/2] trace: Add simple tracing support Stefan Hajnoczi
2010-05-21 9:42 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-21 9:49 ` Stefan Hajnoczi
2010-05-21 9:49 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-21 11:13 ` Jan Kiszka
2010-05-21 11:13 ` [Qemu-devel] " Jan Kiszka
2010-05-21 13:10 ` Stefan Hajnoczi
2010-05-21 13:10 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-21 13:22 ` Jan Kiszka
2010-05-21 13:22 ` [Qemu-devel] " Jan Kiszka
2010-05-21 12:37 ` [Qemu-devel] " Anthony Liguori
2010-05-21 13:46 ` Jan Kiszka
2010-05-21 13:46 ` Jan Kiszka
2010-05-21 14:03 ` Anthony Liguori
2010-05-21 14:03 ` Anthony Liguori
2010-05-21 16:52 ` Jan Kiszka
2010-05-21 16:52 ` Jan Kiszka
2010-05-21 20:49 ` Stefan Hajnoczi
2010-05-21 20:49 ` Stefan Hajnoczi
2010-05-21 21:26 ` Christoph Hellwig
2010-05-21 21:26 ` Christoph Hellwig
2010-05-21 21:37 ` Jan Kiszka
2010-05-21 21:37 ` Jan Kiszka
2010-05-21 21:06 ` Anthony Liguori
2010-05-21 21:06 ` Anthony Liguori
2010-05-21 21:41 ` Jan Kiszka [this message]
2010-05-21 21:41 ` Jan Kiszka
2010-05-21 21:58 ` Anthony Liguori
2010-05-21 21:58 ` Anthony Liguori
2010-05-21 9:42 ` [PATCH 2/2] trace: Trace write requests in virtio-blk, multiwrite, and paio_submit Stefan Hajnoczi
2010-05-21 9:42 ` [Qemu-devel] " Stefan Hajnoczi
2010-05-21 11:27 ` [Qemu-devel] [RFC 0/2] Tracing Prerna Saxena
2010-05-21 11:27 ` Prerna Saxena
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=4BF6FE1D.9020804@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--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 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.