linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Javi Merino <javi.merino@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Dave P Martin <Dave.Martin@arm.com>,
	Ingo Molnar <mingo@redhat.com>
Subject: Re: [RESEND PATCH v2 1/2] tracing: Add array printing helpers
Date: Fri, 16 Jan 2015 10:14:14 +0000	[thread overview]
Message-ID: <20150116101413.GA2898@e104805> (raw)
In-Reply-To: <20150115212202.7939072a@grimm.local.home>

On Fri, Jan 16, 2015 at 02:22:02AM +0000, Steven Rostedt wrote:
> On Thu, 15 Jan 2015 16:50:58 +0000
> Javi Merino <javi.merino@arm.com> wrote:
>  
> > +const char *
> > +ftrace_print_array_seq(struct trace_seq *p, const void *buf, int
> > buf_len,
> > +		       size_t el_size)
> > +{
> > +	const char *ret = trace_seq_buffer_ptr(p);
> > +	const char *prefix = "";
> > +	void *ptr = (void *)buf;
> > +
> > +	trace_seq_putc(p, '{');
> > +
> > +	while (ptr < buf + buf_len) {
> > +		switch (el_size) {
> > +		case 8:
> > +			trace_seq_printf(p, "%s0x%x", prefix,
> > +					 *(u8 *)ptr);
> > +			break;
> > +		case 16:
> > +			trace_seq_printf(p, "%s0x%x", prefix,
> > +					 *(u16 *)ptr);
> > +			break;
> > +		case 32:
> > +			trace_seq_printf(p, "%s0x%x", prefix,
> > +					 *(u32 *)ptr);
> > +			break;
> > +		case 64:
> > +			trace_seq_printf(p, "%s0x%llx", prefix,
> > +					 *(u64 *)ptr);
> > +			break;
> > +		default:
> > +			BUG();
> 
> BUG() is a bit extreme don't you think? I'm not sure it even deserves a
> WARN_ON().

Ok, I used BUG() because that's what you suggested:

http://article.gmane.org/gmane.linux.kernel/1846749

The only way I could think of turning it into a BUILD_BUG was by
moving it to the __print_array macro, but I think it's ugly.

> I would suggest doing:
> 
> 			trace_seq_printf(p, "BAD SIZE:%d 0x%x", el_size,
> 					*(u8 *)ptr);
> 			el_size = 8;
> 
> No need to go crashing the kernel or even messing with dmesg over
> somebody's tracepoint mistake.

Ok, I'll change it to that.

> The rest looks fine.
> 
> > +		}
> > +		prefix = ",";
> > +		ptr += el_size / 8;
> > +	}
> > +
> > +	trace_seq_putc(p, '}');
> > +	trace_seq_putc(p, 0);
> 
> I need to add a trace_seq_terminate() for this.

That would make it more readable.  Cheers,
Javi

  reply	other threads:[~2015-01-16 10:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15 16:50 [RESEND PATCH v2 1/2] tracing: Add array printing helpers Javi Merino
2015-01-15 16:50 ` [RESEND PATCH v2 2/2] tools lib traceevent: Add support for __print_array() Javi Merino
2015-01-16  2:35   ` Steven Rostedt
2015-01-16 11:18     ` Javi Merino
2015-01-16  2:22 ` [RESEND PATCH v2 1/2] tracing: Add array printing helpers Steven Rostedt
2015-01-16 10:14   ` Javi Merino [this message]
2015-01-16 13:30     ` 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=20150116101413.GA2898@e104805 \
    --to=javi.merino@arm.com \
    --cc=Dave.Martin@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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).