From: Robert Richter <robert.richter@amd.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>,
oprofile-list@lists.sourceforge.net,
Paul Mackerras <paulus@samba.org>, cel <cel@linux.vnet.ibm.com>
Subject: Re: powerpc/cell/oprofile: fix mutex locking for spu-oprofile
Date: Wed, 20 Aug 2008 14:39:08 +0200 [thread overview]
Message-ID: <20080820123907.GP13011@erda.amd.com> (raw)
In-Reply-To: <200808201405.32101.arnd@arndb.de>
On 20.08.08 14:05:31, Arnd Bergmann wrote:
> On Wednesday 20 August 2008, Robert Richter wrote:
> > I am fine with the changes with the exception of removing
> > add_event_entry() from include/linux/oprofile.h. Though there is no
> > usage of the function also in other architectures anymore, this change
> > in the API should be discussed on the oprofile mailing list. Please
> > separate the change in a different patch and submit it to the mailing
> > list. If there are no objections then, this change can go upstream as
> > well.
>
> As an explanation, the removal of add_event_entry is the whole point
> of this patch. add_event_entry must only be called with buffer_mutex
> held, but buffer_mutex itself is not exported.
Thanks for pointing this out.
> I'm pretty sure that no other user of add_event_entry exists, as it
> was exported specifically for the SPU support and that never worked.
> Any other (theoretical) code using it would be broken in the same way
> and need a corresponding fix.
>
> We can easily leave the declaration in place, but I'd recommend removing
> it eventually. If you prefer to keep it, how about marking it as
> __deprecated?
No, since this is broken by design we remove it. The patch can go
upstream as it is.
Thanks,
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2008-08-20 12:39 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 [this message]
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
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=20080820123907.GP13011@erda.amd.com \
--to=robert.richter@amd.com \
--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=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