qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v5 06/10] trace-state: add "-trace events" argum


From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] [PATCH v5 06/10] trace-state: add "-trace events" argument to control initial state
Date: Fri, 15 Jul 2011 10:40:30 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Tue, Jun 28, 2011 at 06:53:34PM +0200, LluĂ­s wrote:
> diff --git a/docs/tracing.txt b/docs/tracing.txt
> index 017ff59..8f6e5c9 100644
> --- a/docs/tracing.txt
> +++ b/docs/tracing.txt
> @@ -129,6 +129,9 @@ This functionality is also provided through monitor 
> commands:
>  * trace-event NAME on|off
>    Enable/disable a given trace event.
>  
> +The "-trace events=<file>" command line argument can be used to enable the
> +events listed in <file> from the very beginning of the program.

Please document the syntax of the file: one event name per line.

> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -2394,17 +2394,29 @@ Normally QEMU loads a configuration file from 
> @var{sysconfdir}/qemu.conf and
>  option will prevent QEMU from loading these configuration files at startup.
>  ETEXI
>  DEF("trace", HAS_ARG, QEMU_OPTION_trace,
> -    "-trace\n"
> -    "                Specify a trace file to log traces to\n",
> +    "-trace [events=<file>][,file=<file>]\n"
> +    "                specify tracing options\n",
>      QEMU_ARCH_ALL)
>  STEXI
> -HXCOMM This line is not accurate, as the option is backend-specific but HX 
> does
> -HXCOMM not support conditional compilation of text.
> address@hidden -trace
> +HXCOMM This line is not accurate, as some sub-options are backend-specific 
> but
> +HXCOMM HX does not support conditional compilation of text.
> address@hidden -trace address@hidden,address@hidden
>  @findex -trace
> -Specify a trace file to log output traces to.
> +
> +Specify tracing options.
> +
> address@hidden @option
> address@hidden address@hidden
> +Immediately enable events listed in @var{file}.
> +The file must contain one event name (as listed in the @var{trace-events} 
> file)
> +per line.
> +
> +This option is not available when using the @var{nop} tracing backend.
> address@hidden address@hidden

This option is only available when using the @var{simple} tracing
backend.

(nop, ust, dtrace, stderr don't support it)

Stefan



reply via email to

[Prev in Thread] Current Thread [Next in Thread]