From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] trace: add ability to do simple printf logging via systemtap
Date: Fri, 18 Jan 2019 10:44:16 +0000 [thread overview]
Message-ID: <20190118104416.GF21579@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190117145207.31212-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
On Thu, Jan 17, 2019 at 02:52:07PM +0000, Daniel P. Berrangé wrote:
Dequeued. I encountered two issues during testing:
1. s/binary/file/ in qemu-trace-stap's which() function:
diff --git a/scripts/qemu-trace-stap b/scripts/qemu-trace-stap
index b2eb41fbb0..3b4ec5e9b9 100755
--- a/scripts/qemu-trace-stap
+++ b/scripts/qemu-trace-stap
@@ -37,7 +37,7 @@ def which(file):
if os.path.exists(os.path.join(path, file)):
return os.path.join(path, file)
- print("Unable to find '%s' in $PATH" % binary)
+ print("Unable to find '%s' in $PATH" % file)
sys.exit(1)
2. The tpm_crb_mmio_read trace event's TARGET_FMT_plx format specifier
macro isn't handled. stap sees a literal "TARGET_FMT_plx" string and
reports that the number of format string arguments is incorrect:
semantic error: Wrong number of args to formatted print operator: identifier 'printf' at :9189:5
source: printf("%d@%d tpm_crb_mmio_read CRB read 0x TARGET_FMT_plx len:%u val: 0x%x\n", pid(), gettimeofday_ns(), addr, size, val)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2019-01-18 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 14:52 [Qemu-devel] [PATCH] trace: add ability to do simple printf logging via systemtap Daniel P. Berrangé
2019-01-18 10:05 ` Stefan Hajnoczi
2019-01-18 10:18 ` Daniel P. Berrangé
2019-01-18 10:44 ` Stefan Hajnoczi [this message]
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=20190118104416.GF21579@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=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).