From: Mark Wu <wudxw@vnet.linux.ibm.com>
To: Mark Wu <wudxw@linux.vnet.ibm.com>
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/6] trace: Add support for trace events grouping
Date: Thu, 13 Oct 2011 16:10:56 +0800 [thread overview]
Message-ID: <4E969D10.4060808@vnet.linux.ibm.com> (raw)
In-Reply-To: <1318439659-7525-1-git-send-email-wudxw@linux.vnet.ibm.com>
On 10/13/2011 01:14 AM, Mark Wu wrote:
> This series add support for trace events grouping. The state of a given group
> of trace events can be queried or changed in bulk by the following monitor
> commands:
>
> * info trace-groups
> View available trace event groups and their state. State 1 means enabled,
> state 0 means disabled.
>
> * trace-group NAME on|off
> Enable/disable a given trace event group.
>
> A group of trace events can also be enabled in early running stage through
> adding its group name prefixed with "group:" to trace events list file
> which is passed to "-trace events".
>
> Mark Wu (6):
> trace: Make "tracetool" generate a group list
> trace: Add HMP monitor commands for trace events group
> trace: Add trace events group implementation in the backend "simple"
> trace: Add trace events group implementation in the backend "stderr"
> trace: Enable "-trace events" argument to control initial state of
> groups
> trace: Update doc for trace events group
>
> docs/tracing.txt | 29 ++++++++++++++--
> hmp-commands.hx | 14 ++++++++
> monitor.c | 22 ++++++++++++
> scripts/tracetool | 94 +++++++++++++++++++++++++++++++++++++++++++++++++++-
> trace-events | 88 +++++++++++++++++++++++++++++++++++++++++++++++++
> trace/control.c | 17 +++++++++
> trace/control.h | 9 +++++
> trace/default.c | 15 ++++++++
> trace/simple.c | 30 +++++++++++++++++
> trace/simple.h | 7 ++++
> trace/stderr.c | 32 ++++++++++++++++++
> trace/stderr.h | 7 ++++
> 12 files changed, 359 insertions(+), 5 deletions(-)
>
Sorry, there're some coding style problems in the patches. I have fixed
them and will send out later in order to see if there's any other
problem coming up. :)
next prev parent reply other threads:[~2011-10-13 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 17:14 [Qemu-devel] [PATCH 0/6] trace: Add support for trace events grouping Mark Wu
2011-10-12 17:14 ` [Qemu-devel] [PATCH 1/6] trace: Make "tracetool" generate a group list Mark Wu
2011-10-14 1:48 ` Sheldon
2011-10-12 17:14 ` [Qemu-devel] [PATCH 2/6] trace: Add HMP monitor commands for trace events group Mark Wu
2011-10-12 17:14 ` [Qemu-devel] [PATCH 3/6] trace: Add trace events group implementation in the backend "simple" Mark Wu
2011-10-12 20:46 ` Ryan Harper
2011-10-12 17:14 ` [Qemu-devel] [PATCH 4/6] trace: Add trace events group implementation in the backend "stderr" Mark Wu
2011-10-12 17:14 ` [Qemu-devel] [PATCH 5/6] trace: Enable "-trace events" argument to control initial state of groups Mark Wu
2011-10-12 17:14 ` [Qemu-devel] [PATCH 6/6] trace: Update doc for trace events group Mark Wu
2011-10-13 8:10 ` Mark Wu [this message]
2011-10-14 12:16 ` [Qemu-devel] [PATCH 0/6] trace: Add support for trace events grouping 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=4E969D10.4060808@vnet.linux.ibm.com \
--to=wudxw@vnet.linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wudxw@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).