From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vince@deater.net>
Cc: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
adrian.hunter@intel.com, tglx@linutronix.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf: Update perf_event_type documentation
Date: Thu, 25 Jul 2013 12:04:51 +0200 [thread overview]
Message-ID: <20130725100451.GJ27075@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.02.1307241348250.7828@pianoman.cluster.toy>
On Wed, Jul 24, 2013 at 01:54:00PM -0400, Vince Weaver wrote:
> On Tue, 23 Jul 2013, tip-bot for Peter Zijlstra wrote:
>
> > Commit-ID: a5cdd40c9877e9aba704c020fd65d26b5cfecf18
> > Gitweb: http://git.kernel.org/tip/a5cdd40c9877e9aba704c020fd65d26b5cfecf18
> > Author: Peter Zijlstra <peterz@infradead.org>
> > AuthorDate: Tue, 16 Jul 2013 17:09:07 +0200
> > Committer: Ingo Molnar <mingo@kernel.org>
> > CommitDate: Tue, 23 Jul 2013 12:17:08 +0200
> >
> > perf: Update perf_event_type documentation
> >
> > Due to a discussion with Adrian I had a good look at the perf_event_type record
> > layout and found the documentation to be somewhat unclear.
>
> This code makes a lot of code changes considering it is "updating
> documentation".
>
> Also, will code following this "documentation" be backward compatible?
>
> Meaning, if you have code that depends on the new fields you've added
> and run on older kernels, will you get sane results? Or will the code
> get garbage and/or segfault in the sample_id fields because you read
> past the end of valid data?
I didn't add any fields, this is simply catching up with what was
already there. But yes, this is very much intended to be compatible.
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index 5e2bce9..1274114 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -4462,20 +4462,6 @@ void perf_output_sample(struct perf_output_handle *handle,
> > }
> > }
> >
> > - if (!event->attr.watermark) {
> > - int wakeup_events = event->attr.wakeup_events;
> > -
> > - if (wakeup_events) {
> > - struct ring_buffer *rb = handle->rb;
> > - int events = local_inc_return(&rb->events);
> > -
> > - if (events >= wakeup_events) {
> > - local_sub(wakeup_events, &rb->events);
> > - local_inc(&rb->wakeup);
> > - }
> > - }
> > - }
> > -
> > if (sample_type & PERF_SAMPLE_BRANCH_STACK) {
> > if (data->br_stack) {
> > size_t size;
> > @@ -4511,16 +4497,31 @@ void perf_output_sample(struct perf_output_handle *handle,
> > }
> > }
> >
> > - if (sample_type & PERF_SAMPLE_STACK_USER)
> > + if (sample_type & PERF_SAMPLE_STACK_USER) {
> > perf_output_sample_ustack(handle,
> > data->stack_user_size,
> > data->regs_user.regs);
> > + }
> >
> > if (sample_type & PERF_SAMPLE_WEIGHT)
> > perf_output_put(handle, data->weight);
> >
> > if (sample_type & PERF_SAMPLE_DATA_SRC)
> > perf_output_put(handle, data->data_src.val);
> > +
> > + if (!event->attr.watermark) {
> > + int wakeup_events = event->attr.wakeup_events;
> > +
> > + if (wakeup_events) {
> > + struct ring_buffer *rb = handle->rb;
> > + int events = local_inc_return(&rb->events);
> > +
> > + if (events >= wakeup_events) {
> > + local_sub(wakeup_events, &rb->events);
> > + local_inc(&rb->wakeup);
> > + }
> > + }
> > + }
> > }
I suppose you're 'complaining' about these changes? Yeah, maybe I should
have split them up in a separate patch.
I moved the watermark code from somewhere in the middle of actually
doing the output to the end (where it once was) and added a 'missing'
pair of curlies.
I noticed both oddities when looking at the code to verify the output
format which was updated in the other hunks.
It should be a NOP functionality wise.
next prev parent reply other threads:[~2013-07-25 10:05 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 13:12 [PATCH V5 00/12] perf tools: some fixes and tweaks Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 01/12] perf tools: add debug prints Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 02/12] perf tools: allow non-matching sample types Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 03/12] perf tools: add pid to struct thread Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 04/12] perf tools: change machine__findnew_thread() to set thread pid Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 05/12] perf tools: tidy up sample parsing overflow checking Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 06/12] perf tools: remove unnecessary callchain validation Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 07/12] perf tools: remove references to struct ip_event Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 08/12] perf tools: move " Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 09/12] perf: make events stream always parsable Adrian Hunter
2013-07-11 15:43 ` David Ahern
2013-07-11 17:16 ` David Ahern
2013-07-12 6:42 ` Adrian Hunter
2013-07-12 9:56 ` Peter Zijlstra
2013-07-12 12:56 ` Adrian Hunter
2013-07-12 14:55 ` Peter Zijlstra
2013-07-15 6:14 ` Adrian Hunter
2013-07-15 11:53 ` Stephane Eranian
2013-07-15 12:09 ` Adrian Hunter
2013-07-16 6:49 ` Adrian Hunter
2013-07-16 15:09 ` Peter Zijlstra
2013-07-17 4:10 ` Stephane Eranian
2013-07-17 12:44 ` Adrian Hunter
2013-07-24 3:55 ` [tip:perf/core] perf: Update perf_event_type documentation tip-bot for Peter Zijlstra
2013-07-24 17:54 ` Vince Weaver
2013-07-25 6:22 ` Adrian Hunter
2013-07-25 12:34 ` Vince Weaver
2013-07-25 16:27 ` Peter Zijlstra
2013-07-26 3:24 ` Vince Weaver
2013-07-26 8:55 ` Peter Zijlstra
2013-07-26 3:20 ` Vince Weaver
2013-07-26 8:57 ` Peter Zijlstra
2013-07-27 3:20 ` Vince Weaver
2013-07-25 10:04 ` Peter Zijlstra [this message]
2013-07-25 12:31 ` Vince Weaver
2013-07-25 12:39 ` David Ahern
2013-09-13 21:31 ` Vince Weaver
2013-09-13 21:42 ` Peter Zijlstra
2013-07-11 13:12 ` [PATCH V5 10/12] perf tools: add support for PERF_SAMPLE_IDENTFIER Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 11/12] perf tools: expand perf_event__synthesize_sample() Adrian Hunter
2013-07-11 13:12 ` [PATCH V5 12/12] perf tools: add a sample parsing test Adrian Hunter
2013-07-16 12:48 ` Jiri Olsa
2013-07-17 11:02 ` Adrian Hunter
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=20130725100451.GJ27075@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--cc=vince@deater.net \
/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
Powered by JetHome