From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@au1.ibm.com>
Cc: Paul Mackerras <paulus@samba.org>,
Maynard Johnson <mpjohn@us.ibm.com>,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc: Fix bug where perf_counters breaks oprofile
Date: Mon, 14 Sep 2009 22:28:36 -0400 [thread overview]
Message-ID: <20090915022836.GF12372@zod.rchland.ibm.com> (raw)
In-Reply-To: <1252976208.8375.181.camel@pasglop>
On Tue, Sep 15, 2009 at 10:56:47AM +1000, Benjamin Herrenschmidt wrote:
>On Mon, 2009-09-14 at 16:43 -0400, Josh Boyer wrote:
>> On Mon, Sep 14, 2009 at 03:14:02PM -0500, Maynard Johnson wrote:
>> >Maynard Johnson wrote:
>> >> Paul Mackerras wrote:
>> >>> Currently there is a bug where if you use oprofile on a pSeries
>> >>> machine, then use perf_counters, then use oprofile again, oprofile
>> >>> will not work correctly; it will lose the PMU configuration the next
>> >>> time the hypervisor does a partition context switch, and thereafter
>> >>> won't count anything.
>> >Ben,
>> >Is there any way to get this bug fix into 2.6.31 or is the window closed? Once the problem occurs, you can't get oprofile to work again without a reboot. Really would be nice (for many reasons) to get this fixed in .31.
>>
>> .31 is already released. Could probably get it into a -stable .31 kernel
>> though.
>
>The fix is already upstream as well no ?
Sort of. It's in your next branch, but not in Linus' tree.
Anyway, some people like to have particular versions work so -stable is good
regardless :).
josh
prev parent reply other threads:[~2009-09-15 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 11:26 [PATCH] powerpc: Fix bug where perf_counters breaks oprofile Paul Mackerras
2009-09-09 13:31 ` Maynard Johnson
2009-09-14 20:14 ` Maynard Johnson
2009-09-14 20:43 ` Josh Boyer
2009-09-15 0:56 ` Benjamin Herrenschmidt
2009-09-15 2:28 ` Josh Boyer [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=20090915022836.GF12372@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=benh@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpjohn@us.ibm.com \
--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 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).