From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Daniel Berrange <berrange@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH for-2.10 v2 0/2] trace: fix simpletrace.stp flight recorder mode
Date: Tue, 15 Aug 2017 09:44:28 +0100 [thread overview]
Message-ID: <20170815084430.7128-1-stefanha@redhat.com> (raw)
v2:
* Don't emit event ID mapping records in simpletrace.stp [Daniel Berrange]
The SystemTap flight recorder mode no longer works with simpletrace.stp because
the event ID mapping records are emitted the first time an event fires.
Chances are, the event ID mapping record will not be in ring buffer when the
users wants to print the trace.
This series solves the issue by using the trace-events-all global event
ordering for event IDs for simpletrace.stp.
Stefan Hajnoczi (2):
trace: use static event ID mapping in simpletrace.stp
simpletrace: fix flight recorder --no-header option
scripts/simpletrace.py | 24 +++++++++++++++------
scripts/tracetool/format/simpletrace_stap.py | 31 ++--------------------------
2 files changed, 20 insertions(+), 35 deletions(-)
--
2.13.4
next reply other threads:[~2017-08-15 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-15 8:44 Stefan Hajnoczi [this message]
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
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=20170815084430.7128-1-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).