All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Eric B Munson <emunson@mgebm.net>
Cc: Stephane Eranian <eranian@google.com>,
	mingo@elte.hu, anton@samba.org, linux-kernel@vger.kernel.org,
	paulus@samba.org, hbabu@us.ibm.com
Subject: Re: Oprofile Regression Caused by commit e5d1367f17ba6a6fed5fd8b74e4d5720923e0c25 on PPC
Date: Tue, 18 Oct 2011 16:43:22 +0200	[thread overview]
Message-ID: <1318949002.21167.20.camel@twins> (raw)
In-Reply-To: <20111018135322.GA11530@mgebm.net>

On Tue, 2011-10-18 at 09:53 -0400, Eric B Munson wrote:
> On Wed, 12 Oct 2011, Stephane Eranian wrote:
> 
> > Could be:
> >    a8d757e perf events: Fix slow and broken cgroup context switch code
> > 
> 
> Thanks for the pointer, but the fix was in:
>     facc4307 perf: Optimize event scheduling locking
> 
> This might be a candidate for stable given that oprofile is broken without it.

I might feel much more confident about recommending that if someone
could explain why that patches fixes what exact problem.

  reply	other threads:[~2011-10-18 14:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 20:42 Oprofile Regression Caused by commit e5d1367f17ba6a6fed5fd8b74e4d5720923e0c25 on PPC Eric B Munson
2011-10-10 23:38 ` Eric B Munson
2011-10-11  7:44   ` Peter Zijlstra
2011-10-11  7:47     ` Stephane Eranian
2011-10-11 13:34       ` Eric B Munson
2011-10-11 13:35         ` Stephane Eranian
2011-10-11 13:32     ` Eric B Munson
2011-10-12 16:51     ` Eric B Munson
2011-10-12 20:37       ` Stephane Eranian
2011-10-12 22:20         ` Eric B Munson
2011-10-18 13:53         ` Eric B Munson
2011-10-18 14:43           ` Peter Zijlstra [this message]
2011-10-18 14:50             ` Stephane Eranian
2011-10-18 15:20               ` Eric B Munson

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=1318949002.21167.20.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=anton@samba.org \
    --cc=emunson@mgebm.net \
    --cc=eranian@google.com \
    --cc=hbabu@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.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.