From: Maynard Johnson <maynardj@us.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org,
oprofile-list@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Cbe-oss-dev] [PATCH]Add notification for active Cell SPU tasks
Date: Mon, 04 Dec 2006 09:36:25 -0600 [thread overview]
Message-ID: <45744079.40600@us.ibm.com> (raw)
In-Reply-To: <200612022100.20609.arnd@arndb.de>
Arnd Bergmann wrote:
> On Friday 01 December 2006 21:01, Maynard Johnson wrote:
>
>>+static void notify_spus_active(void)
>>+{
>>+ int node;
>>+ for (node = 0; node < MAX_NUMNODES; node++) {
>>+ struct spu *spu;
>>+ mutex_lock(&spu_prio->active_mutex[node]);
>>+ list_for_each_entry(spu, &spu_prio->active_list[node], list) {
>>+ struct spu_context *ctx = spu->ctx;
>>+ blocking_notifier_call_chain(&spu_switch_notifier,
>>+ ctx ? ctx->object_id : 0, spu);
>>+ }
>>+ mutex_unlock(&spu_prio->active_mutex[node]);
>>+ }
>
>
> I wonder if this is enough for oprofile. Don't you need to access user
> space data of the task running on the SPU? I always assumed you want
No, I don't need anything from the user app besides access to the
executable binary, which I get with copy_from_user, specifying the
'objectid' as from address.
> to do it via get_user or copy_from_user, which obviously doesn't work
> here, when you're running in the oprofile task. Are you using something
> like access_process_vm now?
>
> Arnd <><
next prev parent reply other threads:[~2006-12-04 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 20:01 [PATCH]Add notification for active Cell SPU tasks Maynard Johnson
2006-12-02 20:00 ` [Cbe-oss-dev] " Arnd Bergmann
2006-12-04 15:36 ` Maynard Johnson [this message]
2006-12-04 12:26 ` Luke Browning
2006-12-06 19:30 ` Luke Browning
2006-12-06 22:04 ` Maynard Johnson
2006-12-07 22:58 ` [Cbe-oss-dev] " Arnd Bergmann
2006-12-08 15:04 ` Maynard Johnson
2006-12-08 19:11 ` Luke Browning
2006-12-12 14:47 ` Maynard Johnson
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=45744079.40600@us.ibm.com \
--to=maynardj@us.ibm.com \
--cc=arnd@arndb.de \
--cc=cbe-oss-dev@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=oprofile-list@lists.sourceforge.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 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).