LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Masato Noguchi <Masato.Noguchi@jp.sony.com>,
	"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [patch 2/2] Cell: Wrap master run control bit
Date: Thu, 06 Sep 2007 18:31:20 -0700	[thread overview]
Message-ID: <46E0A9E8.3050701@am.sony.com> (raw)
In-Reply-To: <200709050042.13926.arnd@arndb.de>

Arnd Bergmann wrote:
> On Tuesday 04 September 2007, Geoff Levand wrote:
>> 
>> From: Masato Noguchi <Masato.Noguchi@jp.sony.com>
>> 
>> Add platform specific SPU run control routines.
>> 
>> The current spufs_run_spu() implementation uses the SPU master
>> run control bit (MFC_SR1[S]) to control SPE execution, but the
>> PS3 hypervisor does not support the use of this feature.  This
>> change adds run control wrapper routines.  The  bare metal
>> routines use the master run control bit, and the PS3 specific
>> routines use the priv2 run control register.
>> 
>> Signed-off-by: Masato Noguchi <Masato.Noguchi@jp.sony.com>
>> Signed-off-by: Geoff Levand <geoffrey.levand@am.sony.com>
> 
> Hmm, ok. Since I don't think we'll get to do the right solution
> (unmapping the ps registers on the ps3) that soon, doing this
> patch is at least better than the current situation where we
> end up with an oops every time we leave spu_run.
> 
> It would probably be good to mention the remaining problem
> with the current approach in the changelog and as a comment
> in the ps3 specific functions.

Ok, I did that.

>> @@ -178,6 +179,8 @@ struct spu_management_ops {
>>  	int (*enumerate_spus)(int (*fn)(void *data));
>>  	int (*create_spu)(struct spu *spu, void *data);
>>  	int (*destroy_spu)(struct spu *spu);
>> +	int (*enable_spu)(struct spu_context *ctx);
>> +	int (*disable_spu)(struct spu_context *ctx);
>>  	int (*init_affinity)(void);
>>  };
> 
> Also, I think you should make the return type of the callback
> 'void' since the result is not used anywhere.

Noguchi-san was hesitant to do this.  I also thought lets leave it
as is until we consider the unmapping support, as maybe a return
value might make sense.  Jeremy, if you think it better to return
void, please make the update.

-Geoff

  parent reply	other threads:[~2007-09-07  1:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-04 11:54 [patch 2/2] Cell: Wrap master run control bit Geoff Levand
2007-09-04 22:42 ` Arnd Bergmann
2007-09-04 22:44   ` Arnd Bergmann
2007-09-07  1:26   ` [patch v2] " Geoff Levand
2007-09-07 22:46     ` Arnd Bergmann
2007-09-07  1:31   ` Geoff Levand [this message]
2007-09-07 23:01     ` [patch 2/2] " Arnd Bergmann
2007-09-23 20:50 ` [patch v3] " Geoff Levand
2007-10-24 15:53   ` Geert Uytterhoeven

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=46E0A9E8.3050701@am.sony.com \
    --to=geoffrey.levand@am.sony.com \
    --cc=Masato.Noguchi@jp.sony.com \
    --cc=arnd@arndb.de \
    --cc=linuxppc-dev@ozlabs.org \
    --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