From: Michael Ellerman <michael@ellerman.id.au>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Robert Richter <robert.richter@amd.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, oprofile-list@lists.sourceforge.net,
cel <cel@linux.vnet.ibm.com>,
cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] powerpc/cell/oprofile: fix mutex locking for spu-oprofile
Date: Thu, 21 Aug 2008 20:20:10 +1000 [thread overview]
Message-ID: <1219314010.7827.4.camel@localhost> (raw)
In-Reply-To: <200808211014.42683.arnd@arndb.de>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
On Thu, 2008-08-21 at 10:14 +0200, Arnd Bergmann wrote:
> On Thursday 21 August 2008, Paul Mackerras wrote:
> > Arnd Bergmann writes:
> >
> > > Paul, any chance we can still get this into 2.6.27?
> >
> > Possibly. We'll need a really good explanation for Linus as to why
> > this is needed (what regression or serious bug this fixes) and why it
> > is late. Can you send me something explaining that?
>
> The patch does not fix a regression, the spu-oprofile code basically never
> worked. With the current code in Linux, samples in the profile buffer
> can get corrupted because reader and writer to that buffer use different
> locks for accessing it.
Actually for me it worked[1] a reasonable amount of the time, enough to
be useful. So the spu-oprofile code has always been broken in this way,
but it's not always fatal. So the patch doesn't fix a regression, but it
fixes a serious user-visible bug, which makes it legit rc4 material
IMHO.
[1] that was late last year, so possibly a kernel or two ago.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-08-21 10:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 20:01 [PATCH 2/2] Cell OProfile: SPU mutex lock fix, version 4 Carl Love
2008-08-08 13:26 ` Arnd Bergmann
2008-08-08 22:39 ` [PATCH 2/2] Repost " Carl Love
2008-08-09 13:13 ` please pull cell merge branch Arnd Bergmann
2008-08-10 23:17 ` Paul Mackerras
2008-08-11 7:18 ` [Cbe-oss-dev] " Arnd Bergmann
2008-08-11 7:25 ` powerpc/cell/oprofile: fix mutex locking for spu-oprofile Arnd Bergmann
2008-08-20 11:57 ` Robert Richter
2008-08-20 12:05 ` Arnd Bergmann
2008-08-20 12:39 ` Robert Richter
2008-08-20 14:58 ` Carl Love
2008-08-20 12:39 ` Robert Richter
2008-08-20 13:19 ` Arnd Bergmann
2008-08-21 4:21 ` Paul Mackerras
2008-08-21 8:14 ` [Cbe-oss-dev] " Arnd Bergmann
2008-08-21 10:20 ` Michael Ellerman [this message]
2008-08-21 14:58 ` Carl Love
2008-08-25 6:31 ` Paul Mackerras
2008-08-25 7:55 ` Arnd Bergmann
2008-10-13 14:53 ` Arnd Bergmann
2008-10-13 15:13 ` Robert Richter
2008-08-11 7:25 ` powerpc/cell/oprofile: avoid double free of profile buffer Arnd Bergmann
2008-08-19 11:53 ` Robert Richter
2008-08-11 15:34 ` [Cbe-oss-dev] please pull cell merge branch Carl Love
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=1219314010.7827.4.camel@localhost \
--to=michael@ellerman.id.au \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=cel@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=robert.richter@amd.com \
/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).