From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: "Lluís Vilanova" <vilanova@ac.upc.edu>,
"Stefan Hajnoczi" <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH 1.1 0/2] tracing: QEMU 1.1-rc3+ fixes
Date: Tue, 22 May 2012 17:03:00 +0100 [thread overview]
Message-ID: <1337702582-26368-1-git-send-email-stefanha@linux.vnet.ibm.com> (raw)
Two issues have been reported with the new tracetool Python rewrite:
1. Using parenthesis in ./trace-events format strings produces an exception
from tracetool.py.
2. The 'simple' trace backend event numbering is wrong when the ./trace-events
file contains disabled events (this is the case by default).
These patches fix these issues.
Stefan Hajnoczi (2):
simpletrace: skip disabled trace event numbering
tracetool: allow parenthesis in trace-events format strings
scripts/simpletrace.py | 5 +++--
scripts/tracetool/__init__.py | 2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
--
1.7.10
next reply other threads:[~2012-05-22 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 16:03 Stefan Hajnoczi [this message]
2012-05-22 16:03 ` [Qemu-devel] [PATCH 1.1 1/2] simpletrace: skip disabled trace event numbering Stefan Hajnoczi
2012-05-22 16:03 ` [Qemu-devel] [PATCH 1.1 2/2] tracetool: allow parenthesis in trace-events format strings Stefan Hajnoczi
2012-05-22 18:06 ` Lluís Vilanova
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=1337702582-26368-1-git-send-email-stefanha@linux.vnet.ibm.com \
--to=stefanha@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
/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).