From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] trace: disallow more than 10 arguments per trace event
Date: Wed, 3 May 2017 14:53:39 +0100 [thread overview]
Message-ID: <20170503135339.GE14647@stefanha-x1.localdomain> (raw)
In-Reply-To: <20170426153900.21066-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2666 bytes --]
On Wed, Apr 26, 2017 at 04:39:00PM +0100, Daniel P. Berrange wrote:
> The UST trace backend can only cope with upto 10 arguments. To ensure we
> don't exceed the limit when UST is not compiled in, disallow more than
> 10 arguments upfront.
>
> This prevents the case where:
>
> commit 0fc8aec7de64f2bf83a274a2a38b938ce03425d2
> Author: Zhang Chen <zhangchen.fnst@cn.fujitsu.com>
> Date: Tue Apr 18 10:20:20 2017 +0800
>
> COLO-compare: Optimize tcp compare trace event
>
> Optimize two trace events as one, adjust print format make
> it easy to read. rename trace_colo_compare_pkt_info_src/dst
> to trace_colo_compare_tcp_info.
>
> regressed the fix done in
>
> commit 2dfe5113b11ce0ddb08176ebb54ab7ac4104b413
> Author: Alex Bennée <alex.bennee@linaro.org>
> Date: Fri Oct 28 14:25:59 2016 +0100
>
> net: split colo_compare_pkt_info into two trace events
>
> It seems there is a limit to the number of arguments a UST trace event
> can take and at 11 the previous trace command broke the build. Split the
> trace into a src pkt and dst pkt trace to fix this.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> Message-id: 20161028132559.8324-1-alex.bennee@linaro.org
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>
> Now we get an immediate fail even when UST is disabled:
>
> GEN net/trace.h
> Traceback (most recent call last):
> File "/home/berrange/src/virt/qemu/scripts/tracetool.py", line 154, in <module>
> main(sys.argv)
> File "/home/berrange/src/virt/qemu/scripts/tracetool.py", line 145, in main
> events.extend(tracetool.read_events(fh))
> File "/home/berrange/src/virt/qemu/scripts/tracetool/__init__.py", line 307, in read_events
> event = Event.build(line)
> File "/home/berrange/src/virt/qemu/scripts/tracetool/__init__.py", line 244, in build
> event = Event(name, props, fmt, args)
> File "/home/berrange/src/virt/qemu/scripts/tracetool/__init__.py", line 196, in __init__
> "argument count" % name)
> ValueError: Event 'colo_compare_tcp_info' has more than maximum permitted argument count
> Makefile:96: recipe for target 'net/trace.h-timestamp' failed
>
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
>
> Obviously dont apply this until 0fc8aec7de64f2bf83a274a2a38b938ce03425d2 has
> been reverted :-)
>
> scripts/tracetool/__init__.py | 4 ++++
> 1 file changed, 4 insertions(+)
Thanks, applied to my tracing tree:
https://github.com/stefanha/qemu/commits/tracing
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
prev parent reply other threads:[~2017-05-03 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 15:39 [Qemu-devel] [PATCH] trace: disallow more than 10 arguments per trace event Daniel P. Berrange
2017-04-26 15:41 ` no-reply
2017-04-26 17:54 ` Eric Blake
2017-05-03 13:53 ` 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=20170503135339.GE14647@stefanha-x1.localdomain \
--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).