From: "Daniel P. Berrange" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.10 v2 1/2] trace: use static event ID mapping in simpletrace.stp
Date: Tue, 15 Aug 2017 09:46:52 +0100 [thread overview]
Message-ID: <20170815084652.GC9674@redhat.com> (raw)
In-Reply-To: <20170815084430.7128-2-stefanha@redhat.com>
On Tue, Aug 15, 2017 at 09:44:29AM +0100, Stefan Hajnoczi wrote:
> This is a partial revert of commit
> 7f1b588f20d027730676e627713ae3bbf6baab04 ("trace: emit name <-> ID
> mapping in simpletrace header"), which broke the SystemTap flight
> recorder because event mapping records may not be present in the ring
> buffer when the trace is analyzed. This means simpletrace.py
> --no-header does not know the event ID mapping needed to pretty-print
> the trace.
>
> Instead of numbering events dynamically, use a static event ID mapping
> as dictated by the event order in the trace-events-all file.
>
> The simpletrace.py script also uses trace-events-all so the next patch
> will fix the simpletrace.py --no-header option to take advantage of this
> knowledge.
>
> Cc: Daniel P. Berrange <berrange@redhat.com>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> scripts/tracetool/format/simpletrace_stap.py | 31 ++--------------------------
> 1 file changed, 2 insertions(+), 29 deletions(-)
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2017-08-15 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 8:44 [Qemu-devel] [PATCH for-2.10 v2 0/2] trace: fix simpletrace.stp flight recorder mode Stefan Hajnoczi
2017-08-15 8:44 ` [Qemu-devel] [PATCH for-2.10 v2 1/2] trace: use static event ID mapping in simpletrace.stp Stefan Hajnoczi
2017-08-15 8:46 ` Daniel P. Berrange [this message]
2017-08-15 8:44 ` [Qemu-devel] [PATCH for-2.10 v2 2/2] simpletrace: fix flight recorder --no-header option Stefan Hajnoczi
2017-08-15 8:47 ` Daniel P. Berrange
2017-08-15 8:59 ` [Qemu-devel] [PATCH for-2.10 v2 0/2] trace: fix simpletrace.stp flight recorder mode no-reply
2017-08-15 11:52 ` Stefan Hajnoczi
2017-08-15 11:51 ` 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=20170815084652.GC9674@redhat.com \
--to=berrange@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).