From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Mahesh <mahesh@linux.vnet.ibm.com>,
Ananth Narayan <ananth@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [Tracing][v4 PATCH 2/2] Add documentation for QMP interfaces
Date: Tue, 19 Oct 2010 18:14:26 +0530 [thread overview]
Message-ID: <4CBD92AA.1010503@linux.vnet.ibm.com> (raw)
In-Reply-To: <20101019115750.7ce4a0c7@zephyr>
On 10/19/2010 11:57 AM, Prerna Saxena wrote:
> [PATCH 2/2] Add documentation for QMP commands:
> - query-trace
> - query-trace-events
> - query-trace-file.
>
>
I've been trying ways to avoid building this documentation for other
trace backends ( since these commands are only available with the
'simple' backend ). However, looks like hxtool blindly copies text
between SQMP and EQMP.
I can only think of making hxtool a wee bit intelligent to be able to
parse CONFIG_* options and build documentation accordingly. Is there a
workaround I'm missing ?
--
Prerna Saxena
Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India
next prev parent reply other threads:[~2010-10-19 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 6:19 [Qemu-devel] [Tracing][v4 PATCH 0/2] QMP Query interfaces for tracing Prerna Saxena
2010-10-19 6:25 ` [Qemu-devel] [Tracing][v4 PATCH 1/2] Introduce QMP interfaces Prerna Saxena
2010-10-19 9:12 ` [Qemu-devel] " Stefan Hajnoczi
2010-10-19 6:27 ` [Qemu-devel] [Tracing][v4 PATCH 2/2] Add documentation for " Prerna Saxena
2010-10-19 9:12 ` [Qemu-devel] " Stefan Hajnoczi
2010-10-19 12:44 ` Prerna Saxena [this message]
2010-10-20 19:17 ` Luiz Capitulino
2010-10-21 6:51 ` Prerna Saxena
2010-10-21 12:12 ` 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=4CBD92AA.1010503@linux.vnet.ibm.com \
--to=prerna@linux.vnet.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=mahesh@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.