From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 1/2] vhost-vdpa: fix "unsigned long long" error with stap
Date: Wed, 6 Jan 2021 13:45:41 +0100 [thread overview]
Message-ID: <577fc195-dd47-d70f-dacc-2f784600bf75@redhat.com> (raw)
In-Reply-To: <20210105191721.120463-2-lvivier@redhat.com>
On 05/01/2021 20:17, Laurent Vivier wrote:
> The "%llu" format type is not understood by stap:
>
> $ sudo stap -e 'probe begin{printf ("BEGIN")}' -I .
>
> parse error: invalid or missing conversion specifier
> saw: operator ',' at ./qemu-system-x86_64-log.stp:15118:101
> source: printf("%d@%d vhost_vdpa_set_log_base dev: %p base: 0x%x size: %llu refcnt: %d fd: %d log: %p\n", pid(), gettimeofday_ns(), dev, base, size, refcnt, fd, log)
> ^
>
> 1 parse error.
> WARNING: tapset "./qemu-system-x86_64-log.stp" has errors, and will be skipped
>
> commit 35e28cb0f210 ("scripts/tracetool: silence SystemTap dtrace(1)
> long long warnings") has already fixed the problem for the dtrace format
> by dynamically replacing "unsigned long long" by "uint64_t", but as it
> seems the problem can happen with any format and this is the only
> occurrence of this type, simply replace it directly by "uint64_t" in the
> trace-events file.
>
> Fixes: 778e67de4cd8 ("vhost-vdpa: add trace-events")
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/virtio/trace-events | 2 +-
> hw/virtio/vhost-vdpa.c | 4 ++--
> 2 files changed, 3 insertions(+), 3 deletions(-)
Ignore this patch, Daniel has proposed a better fix.
Thanks,
Laurent
next prev parent reply other threads:[~2021-01-06 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 19:17 [PATCH 0/2] tracetool: fix log-stap format Laurent Vivier
2021-01-05 19:17 ` [PATCH 1/2] vhost-vdpa: fix "unsigned long long" error with stap Laurent Vivier
2021-01-06 12:45 ` Laurent Vivier [this message]
2021-01-05 19:17 ` [PATCH 2/2] tracetool: fix "PRI" macro decoding Laurent Vivier
2021-01-05 19:44 ` Philippe Mathieu-Daudé
2021-01-06 8:56 ` Laurent Vivier
2021-01-06 12:47 ` Daniel P. Berrangé
2021-01-13 15:14 ` Stefan Hajnoczi
2021-01-05 19:44 ` [PATCH 0/2] tracetool: fix log-stap format Philippe Mathieu-Daudé
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=577fc195-dd47-d70f-dacc-2f784600bf75@redhat.com \
--to=lvivier@redhat.com \
--cc=mst@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).