On Mon, Jan 25, 2021 at 11:35:05AM +, Stefan Hajnoczi wrote:
> Zoltan reminded me that the 'log' backend prints tids/timestamps and this can
> be unwanted in some cases. It's easier to look at trace output without them
> and
> in some cases parsing is also more convenient with them.
>
>
On Mon, Jan 25, 2021 at 08:50:23PM +0100, BALATON Zoltan wrote:
> On Mon, 25 Jan 2021, Stefan Hajnoczi wrote:
> > Zoltan reminded me that the 'log' backend prints tids/timestamps and this
> > can
> > be unwanted in some cases. It's easier to look at trace output without them
> > and
> > in some
On Mon, 25 Jan 2021, Stefan Hajnoczi wrote:
Zoltan reminded me that the 'log' backend prints tids/timestamps and this can
be unwanted in some cases. It's easier to look at trace output without them and
in some cases parsing is also more convenient with them.
Extend -msg timestamp=on|off to
On Mon, Jan 25, 2021 at 03:06:30PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Stefan,
>
> On 1/25/21 12:35 PM, Stefan Hajnoczi wrote:
> > Zoltan reminded me that the 'log' backend prints tids/timestamps and this
> > can
> > be unwanted in some cases. It's easier to look at trace output without
Hi Stefan,
On 1/25/21 12:35 PM, Stefan Hajnoczi wrote:
> Zoltan reminded me that the 'log' backend prints tids/timestamps and this can
> be unwanted in some cases. It's easier to look at trace output without them
> and
> in some cases parsing is also more convenient with them.
>
> Extend -msg
Zoltan reminded me that the 'log' backend prints tids/timestamps and this can
be unwanted in some cases. It's easier to look at trace output without them and
in some cases parsing is also more convenient with them.
Extend -msg timestamp=on|off to control the 'log' backend's tid/timestamp
output.
