From: Markus Armbruster <armbru@redhat.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
maneesh@linux.vnet.ibm.com, ananth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC v2] [PATCH 0/3] Monitor Support for 'simple' trace backend
Date: Fri, 11 Jun 2010 13:42:32 +0200 [thread overview]
Message-ID: <m37hm5lrrr.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20100611003811.2635fa5d@zephyr> (Prerna Saxena's message of "Fri, 11 Jun 2010 00:38:11 +0530")
Prerna Saxena <prerna@linux.vnet.ibm.com> writes:
> This is v2 of monitor commands based on Stefan's trace framework :
> ( http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02407.html )
>
> This adds the following monitor commands for the 'simple' backend:
> - info trace : to view current contents of the trace buffer.
> - info tracepoints : to view all available tracepoints and their
> state.
> - tracepoint NAME on|off: to enable/disable the logging of data from
> tracepoint 'NAME'.
>
>
> Changelog :
> - Command 'info trace' is used to view current contents of buffer, in
> place of 'trace'.
> - Cleanups
Do we want this in QMP?
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Prerna Saxena <prerna@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
kvm@vger.kernel.org, Jan Kiszka <jan.kiszka@siemens.com>,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
maneesh@linux.vnet.ibm.com, ananth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC v2] [PATCH 0/3] Monitor Support for 'simple' trace backend
Date: Fri, 11 Jun 2010 13:42:32 +0200 [thread overview]
Message-ID: <m37hm5lrrr.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <20100611003811.2635fa5d@zephyr> (Prerna Saxena's message of "Fri, 11 Jun 2010 00:38:11 +0530")
Prerna Saxena <prerna@linux.vnet.ibm.com> writes:
> This is v2 of monitor commands based on Stefan's trace framework :
> ( http://lists.gnu.org/archive/html/qemu-devel/2010-05/msg02407.html )
>
> This adds the following monitor commands for the 'simple' backend:
> - info trace : to view current contents of the trace buffer.
> - info tracepoints : to view all available tracepoints and their
> state.
> - tracepoint NAME on|off: to enable/disable the logging of data from
> tracepoint 'NAME'.
>
>
> Changelog :
> - Command 'info trace' is used to view current contents of buffer, in
> place of 'trace'.
> - Cleanups
Do we want this in QMP?
next prev parent reply other threads:[~2010-06-11 11:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 19:08 [RFC v2] [PATCH 0/3] Monitor Support for 'simple' trace backend Prerna Saxena
2010-06-10 19:08 ` [Qemu-devel] " Prerna Saxena
2010-06-10 19:15 ` [RFC v2] [PATCH 1/3] Export tdb_hash() Prerna Saxena
2010-06-10 19:15 ` [Qemu-devel] " Prerna Saxena
2010-06-11 17:54 ` Luiz Capitulino
2010-06-11 17:54 ` [Qemu-devel] " Luiz Capitulino
2010-06-10 19:20 ` [RFC v2] [PATCH 2/3] Monitor command 'info trace' Prerna Saxena
2010-06-10 19:20 ` [Qemu-devel] " Prerna Saxena
2010-06-10 19:24 ` [RFC v2] [PATCH 3/3] Toggle tracepoint state Prerna Saxena
2010-06-10 19:24 ` [Qemu-devel] " Prerna Saxena
2010-06-11 11:42 ` Markus Armbruster [this message]
2010-06-11 11:42 ` [Qemu-devel] [RFC v2] [PATCH 0/3] Monitor Support for 'simple' trace backend Markus Armbruster
2010-06-11 12:08 ` Jan Kiszka
2010-06-11 12:08 ` Jan Kiszka
2010-06-11 17:56 ` Luiz Capitulino
2010-06-11 17:56 ` Luiz Capitulino
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=m37hm5lrrr.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=maneesh@linux.vnet.ibm.com \
--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.