From: Stefan Hajnoczi <stefanha@gmail.com>
To: Lluís <xscript@gmx.net>
Cc: qemu-devel@nongnu.org, chouteau@adacore.com
Subject: Re: [Qemu-devel] [PATCH v2 06/11] trace: generalize the "property" concept in the trace-events file
Date: Sat, 23 Apr 2011 15:22:12 +0100 [thread overview]
Message-ID: <BANLkTinz5RtzYLYCOFpPQTvZJ36zeAqB7w@mail.gmail.com> (raw)
In-Reply-To: <20110406183431.22854.56191.stgit@ginnungagap.bsc.es>
On Wed, Apr 6, 2011 at 7:34 PM, Lluís <xscript@gmx.net> wrote:
> diff --git a/docs/tracing.txt b/docs/tracing.txt
> index 34b0901..a9fd85b 100644
> --- a/docs/tracing.txt
> +++ b/docs/tracing.txt
> @@ -38,7 +38,7 @@ generate code for the trace events. Trace events are invoked directly from
> source code like this:
>
> #include "trace.h" /* needed for trace event prototype */
> -
> +
> void *qemu_malloc(size_t size)
> {
> void *ptr;
> @@ -98,7 +98,7 @@ portability macros, ensure they are preceded and followed by double quotes:
> 4. Name trace events after their function. If there are multiple trace events
> in one function, append a unique distinguisher at the end of the name.
>
> -5. Declare trace events with the "disable" keyword. Some trace events can
> +5. Declare trace events with the "disable" property. Some trace events can
> produce a lot of output and users are typically only interested in a subset
> of trace events. Marking trace events disabled by default saves the user
> from having to manually disable noisy trace events.
> @@ -168,7 +168,7 @@ The st_change_trace_event_state() function can be used to enable or disable trac
> events at runtime inside QEMU:
>
> #include "trace.h"
> -
> +
> st_change_trace_event_state("virtio_irq", true); /* enable */
> [...]
> st_change_trace_event_state("virtio_irq", false); /* disable */
Tailing whitespace is there due to wiki formatting. Please do not remove it.
The rest looks good.
Stefan
next prev parent reply other threads:[~2011-04-23 14:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 18:33 [Qemu-devel] [RFC][PATCH v2 00/11] trace-state: make the behaviour of "disable" consistent across all backends Lluís
2011-04-06 18:33 ` [Qemu-devel] [PATCH v2 01/11] minor whitespace/indentation fixes Lluís
2011-04-23 14:19 ` Stefan Hajnoczi
2011-04-26 10:00 ` Markus Armbruster
2011-04-06 18:33 ` [Qemu-devel] [PATCH v2 02/11] docs/tracing.txt: minor documentation fixes Lluís
2011-04-06 18:34 ` [Qemu-devel] [PATCH v2 03/11] trace: [ust] fix generation of 'trace.c' on events without args Lluís
2011-04-06 18:34 ` [Qemu-devel] [PATCH v2 04/11] trace: [trace-events] fix print formats in some events Lluís
2011-04-06 18:34 ` [Qemu-devel] [PATCH v2 05/11] trace: [simple] minor code fixes on conditional compilation Lluís
2011-04-23 14:20 ` Stefan Hajnoczi
2011-04-06 18:34 ` [Qemu-devel] [PATCH v2 06/11] trace: generalize the "property" concept in the trace-events file Lluís
2011-04-23 14:22 ` Stefan Hajnoczi [this message]
2011-04-06 18:34 ` [Qemu-devel] [PATCH v2 07/11] trace-state: always use the "nop" backend on events with the "disable" keyword Lluís
2011-04-06 18:34 ` [Qemu-devel] [PATCH v2 08/11] trace-state: [simple] disable all trace points by default Lluís
2011-04-06 18:34 ` [Qemu-devel] [PATCH v2 09/11] trace-state: [simple] add "-trace events" argument to control initial state Lluís
2011-04-06 18:35 ` [Qemu-devel] [PATCH v2 10/11] trace-state: [stderr] add support for dynamically enabling/disabling events Lluís
2011-04-23 14:31 ` Stefan Hajnoczi
2011-04-24 6:24 ` Paolo Bonzini
2011-04-24 9:33 ` Stefan Hajnoczi
2011-04-25 10:27 ` Lluís
2011-04-25 18:10 ` Paolo Bonzini
2011-04-26 12:30 ` Fabien Chouteau
2011-04-26 12:38 ` Stefan Hajnoczi
2011-04-26 12:59 ` Paolo Bonzini
2011-04-26 14:01 ` Lluís
2011-04-06 18:35 ` [Qemu-devel] [PATCH v2 11/11] trace: enable all events Lluís
2011-04-23 14:45 ` [Qemu-devel] [RFC][PATCH v2 00/11] trace-state: make the behaviour of "disable" consistent across all backends 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=BANLkTinz5RtzYLYCOFpPQTvZJ36zeAqB7w@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=chouteau@adacore.com \
--cc=qemu-devel@nongnu.org \
--cc=xscript@gmx.net \
/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).