From: Maynard Johnson <maynardj@us.ibm.com>
To: Carl Love <cel@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org,
oprofile-list <oprofile-list@lists.sf.net>,
cbe-oss-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Updated: Reworked Cell OProfile: SPU mutex lock fix
Date: Thu, 01 May 2008 11:29:34 -0500 [thread overview]
Message-ID: <4819EFEE.4040601@us.ibm.com> (raw)
In-Reply-To: <1209652994.17842.1.camel@carll-linux-desktop>
Carl Love wrote:
> Sorry, looks like my mailer mangled the file.
>
> This is a reworked patch to fix the SPU data storage. Currently, the
> SPU escape sequences and program counter data is being added directly
> into the kernel buffer without holding the buffer_mutex lock. This
> patch changes how the data is stored. A new function,
> oprofile_add_value, is added into the oprofile driver to allow adding
> generic data to the per cpu buffers. This enables a series of calls
> to the oprofile_add_value to enter the needed SPU escape sequences
> and SPU program data into the kernel buffer via the per cpu buffers
> without any additional processing. The oprofile_add_value function is
> generic so it could be used by other architecures as well provided
> the needed postprocessing was added to opreport.
>
> Finally, this patch backs out the changes previously added to the
> oprofile generic code for handling the architecture specific
> ops.sync_start and ops.sync_stop that allowed the architecture
> to skip the per CPU buffer creation.
>
> Signed-off-by: Carl Love <carll@us.ibm.com>
>
Looks fine to me. All of my previous review comments have been addressed.
-Maynard
[snip]
WARNING: multiple messages have this Message-ID (diff)
From: Maynard Johnson <maynardj@us.ibm.com>
To: Carl Love <cel@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
oprofile-list <oprofile-list@lists.sourceforge.net>
Subject: Re: [PATCH] Updated: Reworked Cell OProfile: SPU mutex lock fix
Date: Thu, 01 May 2008 11:29:34 -0500 [thread overview]
Message-ID: <4819EFEE.4040601@us.ibm.com> (raw)
In-Reply-To: <1209652994.17842.1.camel@carll-linux-desktop>
Carl Love wrote:
> Sorry, looks like my mailer mangled the file.
>
> This is a reworked patch to fix the SPU data storage. Currently, the
> SPU escape sequences and program counter data is being added directly
> into the kernel buffer without holding the buffer_mutex lock. This
> patch changes how the data is stored. A new function,
> oprofile_add_value, is added into the oprofile driver to allow adding
> generic data to the per cpu buffers. This enables a series of calls
> to the oprofile_add_value to enter the needed SPU escape sequences
> and SPU program data into the kernel buffer via the per cpu buffers
> without any additional processing. The oprofile_add_value function is
> generic so it could be used by other architecures as well provided
> the needed postprocessing was added to opreport.
>
> Finally, this patch backs out the changes previously added to the
> oprofile generic code for handling the architecture specific
> ops.sync_start and ops.sync_stop that allowed the architecture
> to skip the per CPU buffer creation.
>
> Signed-off-by: Carl Love <carll@us.ibm.com>
>
Looks fine to me. All of my previous review comments have been addressed.
-Maynard
[snip]
next prev parent reply other threads:[~2008-05-01 16:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 14:43 [PATCH] Updated: Reworked Cell OProfile: SPU mutex lock fix Carl Love
2008-05-01 14:43 ` Carl Love
2008-05-01 16:29 ` Maynard Johnson [this message]
2008-05-01 16:29 ` Maynard Johnson
2008-05-02 19:52 ` Maynard Johnson
2008-05-02 19:52 ` Maynard Johnson
2008-05-15 15:39 ` Arnd Bergmann
2008-05-15 15:39 ` Arnd Bergmann
2008-05-15 19:05 ` Carl Love
2008-05-15 19:05 ` Carl Love
2008-05-16 14:22 ` Arnd Bergmann
2008-05-16 14:22 ` Arnd Bergmann
2008-05-16 16:24 ` Carl Love
2008-05-16 16:24 ` 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=4819EFEE.4040601@us.ibm.com \
--to=maynardj@us.ibm.com \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=cel@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=oprofile-list@lists.sf.net \
/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.