From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Daniel Berrange <berrange@redhat.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH 0/2] trace: make the 'log' backend timestamp configurable
Date: Mon, 25 Jan 2021 15:06:30 +0100 [thread overview]
Message-ID: <220bc0d1-4d1d-eeaf-6e2e-66fa33de8f98@redhat.com> (raw)
In-Reply-To: <20210125113507.224287-1-stefanha@redhat.com>
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 timestamp=on|off to control the 'log' backend's tid/timestamp output.
>
> Stefan Hajnoczi (2):
> error: rename error_with_timestamp to message_with_timestamp
> trace: make the 'log' backend timestamp configurable
>
> docs/devel/tracing.txt | 3 +++
> include/qemu/error-report.h | 2 +-
> softmmu/vl.c | 2 +-
> util/qemu-error.c | 4 ++--
> scripts/tracetool/backend/log.py | 19 +++++++++++++------
> 5 files changed, 20 insertions(+), 10 deletions(-)
I applied your series, rebuilt, but nothing changed.
Apparently there is some buildsys rule missing, the
trace files weren't regenerated.
After full tree 'make clean' I could successfully test:
Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Ignoring the buildsys issue:
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Regards,
Phil.
next prev parent reply other threads:[~2021-01-25 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 11:35 [PATCH 0/2] trace: make the 'log' backend timestamp configurable Stefan Hajnoczi
2021-01-25 11:35 ` [PATCH 1/2] error: rename error_with_timestamp to message_with_timestamp Stefan Hajnoczi
2021-01-25 11:35 ` [PATCH 2/2] trace: make the 'log' backend timestamp configurable Stefan Hajnoczi
2021-01-25 14:06 ` Philippe Mathieu-Daudé [this message]
2021-01-25 16:19 ` [PATCH 0/2] " Stefan Hajnoczi
2021-01-25 19:50 ` BALATON Zoltan
2021-01-26 14:01 ` Stefan Hajnoczi
2021-01-26 16:21 ` 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=220bc0d1-4d1d-eeaf-6e2e-66fa33de8f98@redhat.com \
--to=philmd@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).