From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/4] trace: make systemtap easier to use for simple logging
Date: Fri, 18 Jan 2019 17:30:59 +0000 [thread overview]
Message-ID: <20190118173103.4903-1-berrange@redhat.com> (raw)
This is a followup to
v1: https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg04173.html
Changed in v2:
- Fix safety of QXL logging
- Handle format specifier macros is a more reliable manner
- Fix trace-events files missing newline
- Remove use of %m formats
Daniel P. Berrangé (4):
display: ensure qxl log_buf is a nul terminated string
trace: enforce that every trace-events file has a final newline
trace: forbid use of %m in trace event format strings
trace: add ability to do simple printf logging via systemtap
Makefile | 3 +
Makefile.target | 11 +-
docs/devel/tracing.txt | 32 +++++
hw/display/qxl.c | 3 +-
hw/display/trace-events | 2 +-
hw/gpio/trace-events | 2 +-
hw/vfio/pci.c | 2 +-
hw/vfio/trace-events | 2 +-
scripts/qemu-trace-stap | 167 +++++++++++++++++++++++++++
scripts/tracetool/__init__.py | 6 +
scripts/tracetool/format/log_stap.py | 127 ++++++++++++++++++++
11 files changed, 351 insertions(+), 6 deletions(-)
create mode 100755 scripts/qemu-trace-stap
create mode 100644 scripts/tracetool/format/log_stap.py
--
2.20.1
next reply other threads:[~2019-01-18 17:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 17:30 Daniel P. Berrangé [this message]
2019-01-18 17:31 ` [Qemu-devel] [PATCH v2 1/4] display: ensure qxl log_buf is a nul terminated string Daniel P. Berrangé
2019-01-18 17:40 ` Eric Blake
2019-01-18 17:42 ` Daniel P. Berrangé
2019-01-21 7:14 ` Gerd Hoffmann
2019-01-21 10:45 ` Stefan Hajnoczi
2019-01-22 14:17 ` Daniel P. Berrangé
2019-01-18 17:31 ` [Qemu-devel] [PATCH v2 2/4] trace: enforce that every trace-events file has a final newline Daniel P. Berrangé
2019-01-18 17:42 ` Eric Blake
2019-01-22 14:43 ` Daniel P. Berrangé
2019-01-21 10:47 ` Stefan Hajnoczi
2019-01-18 17:31 ` [Qemu-devel] [PATCH v2 3/4] trace: forbid use of %m in trace event format strings Daniel P. Berrangé
2019-01-18 17:50 ` Eric Blake
2019-01-18 22:50 ` Alex Williamson
2019-01-22 14:32 ` Daniel P. Berrangé
2019-01-22 17:19 ` Eric Blake
2019-01-22 17:23 ` Daniel P. Berrangé
2019-01-22 18:10 ` Eric Blake
2019-10-18 9:31 ` Thomas Huth
2019-10-18 9:34 ` Daniel P. Berrangé
2019-01-18 17:31 ` [Qemu-devel] [PATCH v2 4/4] trace: add ability to do simple printf logging via systemtap Daniel P. Berrangé
2019-01-18 18:14 ` Eric Blake
2019-01-21 10:53 ` Stefan Hajnoczi
2019-01-22 14:34 ` Daniel P. Berrangé
2019-01-22 14:39 ` Daniel P. Berrangé
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=20190118173103.4903-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=kraxel@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).