From: Jiri Olsa <jolsa@redhat.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Jiri Olsa <jolsa@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
lkml <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [RFC/PATCH] lib/vsprintf: Add support to store cpumask
Date: Wed, 29 Jun 2016 09:12:07 +0200 [thread overview]
Message-ID: <20160629071207.GA14163@krava> (raw)
In-Reply-To: <87r3bhgge8.fsf@rasmusvillemoes.dk>
On Tue, Jun 28, 2016 at 11:19:59PM +0200, Rasmus Villemoes wrote:
SNIP
> > - save_arg(void *);
> > + if (spec.cpumask) {
>
> As I hinted in the other mail, I think it's better just to put the
> fmt[1]=='b' here and not change struct printf_spec.
>
> > + /*
> > + * Store entire cpumask directly to buffer
> > + * instead of storing just a pointer.
> > + */
> > + struct cpumask *mask = va_arg(args, void *);
> > +
> > + str = PTR_ALIGN(str, sizeof(u32));
> > +
> > + if (str + sizeof(*mask) <= end)
> > + cpumask_copy((struct cpumask *) str, mask);
>
> A cpumask is an array of longs. Why is u32-alignment enough for that?
> cpumask_copy may end up compiling to a simple "*dst = *src", and even if
> this is a memcpy(), the same 4-but-possibly-not-8 byte aligned
> pointer is created below in bstr_printf which is then passed on to
> pointer() and then bitmap_* which certainly expects an unsigned long*.
hum, the binary buffer is copied after to trace buffer which
has 32bit alignment I think, so bigger alignment breaks the
data.. also the save_arg macro does 32bit alignment for 8 bytes
anyway, I haven't checked deeply on this, was just hunting
wrong cpumask, now with Steven's changes I'm ok to drop it ;-)
thanks,
jirka
prev parent reply other threads:[~2016-06-29 7:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 15:34 [RFC/PATCH] lib/vsprintf: Add support to store cpumask Jiri Olsa
2016-06-28 16:26 ` Steven Rostedt
2016-06-28 19:27 ` Rasmus Villemoes
2016-06-28 19:56 ` Steven Rostedt
2016-06-28 21:50 ` Rasmus Villemoes
2016-06-28 22:05 ` Steven Rostedt
2016-06-28 22:06 ` Steven Rostedt
2016-06-29 6:43 ` Jiri Olsa
2016-06-29 15:42 ` Steven Rostedt
2016-06-28 21:19 ` Rasmus Villemoes
2016-06-29 7:12 ` Jiri Olsa [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=20160629071207.GA14163@krava \
--to=jolsa@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.