public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.cz>
Cc: Qu Wenruo <wqu@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2] tools/lib/traceevent, perf tools: Handle %pU format correctly
Date: Thu, 17 Oct 2019 13:54:23 +0200	[thread overview]
Message-ID: <20191017115423.GH2751@twin.jikos.cz> (raw)
In-Reply-To: <20191017115209.GG2751@twin.jikos.cz>

On Thu, Oct 17, 2019 at 01:52:09PM +0200, David Sterba wrote:
> On Thu, Oct 17, 2019 at 10:28:00AM +0800, Qu Wenruo wrote:
> > [BUG]
> > For btrfs related events, there is a field for fsid, but perf never
> > parse it correctly.
> > 
> >  # perf trace -e btrfs:qgroup_meta_convert xfs_io -f -c "pwrite 0 4k" \
> >    /mnt/btrfs/file1
> >      0.000 xfs_io/77915 btrfs:qgroup_meta_reserve:(nil)U: refroot=5(FS_TREE) type=0x0 diff=2
> >                                                   ^^^^^^ Not a correct UUID
> >      ...
> > 
> > [CAUSE]
> > The pretty_print() function doesn't handle the %pU format correctly.
> > In fact it doesn't handle %pU as uuid at all.
> > 
> > [FIX]
> > Add a new function, print_uuid_arg(), to handle %pU correctly.
> > 
> > Now perf trace can at least print fsid correctly:
> >      0.000 xfs_io/79619 btrfs:qgroup_meta_reserve:23ad1511-dd83-47d4-a79c-e96625a15a6e refroot=5(FS_TREE) type=0x0 diff=2
> > 
> > Signed-off-by: Qu Wenruo <wqu@suse.com>
> > ---
> > Changelog:
> > v2:
> > - Use more comment explaining the finetunings we skipped for %pU*
> > - Use more elegant way to output uuid string
> > ---
> >  tools/lib/traceevent/event-parse.c | 56 ++++++++++++++++++++++++++++++
> >  1 file changed, 56 insertions(+)
> > 
> > diff --git a/tools/lib/traceevent/event-parse.c b/tools/lib/traceevent/event-parse.c
> > index d948475585ce..3c9473f46efe 100644
> > --- a/tools/lib/traceevent/event-parse.c
> > +++ b/tools/lib/traceevent/event-parse.c
> > @@ -18,6 +18,7 @@
> >  #include <errno.h>
> >  #include <stdint.h>
> >  #include <limits.h>
> > +#include <linux/uuid.h>
> >  #include <linux/time64.h>
> >  
> >  #include <netinet/in.h>
> > @@ -4508,6 +4509,45 @@ get_bprint_format(void *data, int size __maybe_unused,
> >  	return format;
> >  }
> >  
> > +static void print_uuid_arg(struct trace_seq *s, void *data, int size,
> > +			   struct tep_event *event, struct tep_print_arg *arg)
> > +{
> > +	unsigned char *buf;
> > +	int i;
> > +
> > +	if (arg->type != TEP_PRINT_FIELD) {
> > +		trace_seq_printf(s, "ARG TYPE NOT FIELID but %d", arg->type);
> > +		return;
> > +	}
> > +
> > +	if (!arg->field.field) {
> > +		arg->field.field = tep_find_any_field(event, arg->field.name);
> > +		if (!arg->field.field) {
> > +			do_warning("%s: field %s not found",
> > +				   __func__, arg->field.name);
> > +			return;
> > +		}
> > +	}
> > +	if (arg->field.field->size < 16) {
> > +		trace_seq_printf(s, "INVALID UUID: size have %u expect 16",
> > +				arg->field.field->size);
> > +		return;
> > +	}
> 
> So if there's an interest for very compact printing loop, something like
> this produces the same output:
> 
> 	for (i = 0; i < 8; i++) {
> 		printf("%02X", buf[i]);
> 		printf("%02X", buf[i]);

Ok, test-before-post failure, this should be

		printf("%02X", buf[2 * i]);
	        printf("%02X", buf[2 * i + 1]);

> 		if (1 <= i && i <= 4)
> 			putchar('-');
> 	}

  reply	other threads:[~2019-10-17 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  2:28 [PATCH v2] tools/lib/traceevent, perf tools: Handle %pU format correctly Qu Wenruo
2019-10-17 11:52 ` David Sterba
2019-10-17 11:54   ` David Sterba [this message]
2019-10-17 12:31     ` Steven Rostedt

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=20191017115423.GH2751@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=wqu@suse.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