Am 25.10.2015 um 22:32 schrieb Paolo Bonzini:
> This series does three things:
>
> 1) add a "-trace [enable=]foo" option to enable one or more trace
> events, and a "-trace help" option to show the list of tracepoints
> (patches 4-5)
>
> 2) change the stderr tracing backend so that it prints to t
Am 25.10.2015 um 22:32 schrieb Paolo Bonzini:
> This series does three things:
>
> 1) add a "-trace [enable=]foo" option to enable one or more trace
> events, and a "-trace help" option to show the list of tracepoints
> (patches 4-5)
>
> 2) change the stderr tracing backend so that it prints to t
On 25/10/2015 14:57, Peter Maydell wrote:
> > Opinions? I would like to have this in 2.5 if there is agreement.
>
> Have you done any performance testing to check that we don't have
> previously-nopped-out tracepoints in hot paths that now result in
> real code being generated?
There definitely
On 25 October 2015 at 13:32, Paolo Bonzini wrote:
> This series does three things:
>
> 1) add a "-trace [enable=]foo" option to enable one or more trace
> events, and a "-trace help" option to show the list of tracepoints
> (patches 4-5)
>
> 2) change the stderr tracing backend so that it prints t
This series does three things:
1) add a "-trace [enable=]foo" option to enable one or more trace
events, and a "-trace help" option to show the list of tracepoints
(patches 4-5)
2) change the stderr tracing backend so that it prints to the
-D log file, and enable it by default. "-trace file=..."
