Re: [PATCH 1/2] perf: Fix the software events state check

[Frederic Weisbecker <fweisbec@gmail.com>]

On Wed, Mar 09, 2011 at 10:28:18AM +0100, Ingo Molnar wrote:
> 
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> 
> > Fix the mistakenly inverted check of events state.
> > 
> > Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> > Cc: Ingo Molnar <mingo@elte.hu>
> > Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Cc: Arnaldo Carvalho de Melo <acme@redhat.com>
> > Cc: Paul Mackerras <paulus@samba.org>
> > Cc: Stephane Eranian <eranian@google.com>
> > ---
> >  kernel/perf_event.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/kernel/perf_event.c b/kernel/perf_event.c
> > index ed253aa..974e2e6 100644
> > --- a/kernel/perf_event.c
> > +++ b/kernel/perf_event.c
> > @@ -5122,7 +5122,7 @@ static int perf_exclude_event(struct perf_event *event,
> >  			      struct pt_regs *regs)
> >  {
> >  	if (event->hw.state & PERF_HES_STOPPED)
> > -		return 0;
> > +		return 1;
> 
> Just wondering, what was/is the practical effect of this bug, and how far back does 
> it go (any need for a -stable tag)?

I wasn't sure about that so I haven't told about the impact in the
changelog.

But now that I put a deeper look into this:

It seems that ->stop() / ->start() are called from perf_adjust_period()
to update the hardware with the new settings of period_left. The events
are stopped to avoid any race with events triggering with a stale period_left
in the hardware level when the software one has been updated, I guess.

So it doesn't seem to fix any existing bug because for ->stop() and ->start()
are only useful for hardware events right now. But we may call ->stop() and
->start() for further purpose later. In fact that paves the way for the event
exclusion patchset I'm about to post.

So it should be .39 material. But a confirmation from Peter would be nice.