From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] trace/ftrace: move snprintf+write from tracepoints to ftrace.c
Date: Tue, 19 Aug 2025 13:16:39 +0100 [thread overview]
Message-ID: <aKRrJySwMXT5YnET@redhat.com> (raw)
In-Reply-To: <20250808091110.23126-1-pbonzini@redhat.com>
On Fri, Aug 08, 2025 at 11:11:10AM +0200, Paolo Bonzini wrote:
> This simplifies the Python code and reduces the size of the tracepoints.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> tests/tracetool/ftrace.h | 26 ++++----------------------
> trace/ftrace.h | 1 +
> trace/ftrace.c | 13 +++++++++++++
> scripts/tracetool/backend/ftrace.py | 13 ++-----------
> 4 files changed, 20 insertions(+), 33 deletions(-)
> diff --git a/trace/ftrace.c b/trace/ftrace.c
> index 9749543d9b2..1d7e1ee6f6d 100644
> --- a/trace/ftrace.c
> +++ b/trace/ftrace.c
> @@ -38,6 +38,19 @@ static int find_mount(char *mount_point, const char *fstype)
> return ret;
> }
>
> +void ftrace_write(const char *fmt, ...)
> +{
> + char ftrace_buf[MAX_TRACE_STRLEN];
> + int unused __attribute__ ((unused));
> + int trlen;
> + va_list ap;
> +
> + va_start(ap, fmt);
> + trlen = vsnprintf(ftrace_buf, MAX_TRACE_STRLEN, fmt, ap);
va_end(ap);
> + trlen = MIN(trlen, MAX_TRACE_STRLEN - 1);
> + unused = write(trace_marker_fd, ftrace_buf, trlen);
> +}
> +
> bool ftrace_init(void)
> {
> char mount_point[PATH_MAX];
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2025-08-19 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 9:11 [PATCH] trace/ftrace: move snprintf+write from tracepoints to ftrace.c Paolo Bonzini
2025-08-19 12:16 ` Daniel P. Berrangé [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=aKRrJySwMXT5YnET@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@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).