Re: [Cbe-oss-dev] [PATCH 14/22] spufs: use SPU master control to prevent wild SPU execution

2007-03-07 Thread Michael Ellerman
On Mon, 2007-03-05 at 02:02 +0100, Arnd Bergmann wrote: > On Friday 02 March 2007, Michael Ellerman wrote: > > There's also the error case for spu_run_init() which skips the master > > stop. I guess that's ok because we've only set the master control in the > > backing store, and the only way that

Re: [Cbe-oss-dev] [PATCH 14/22] spufs: use SPU master control to prevent wild SPU execution

2007-03-04 Thread Arnd Bergmann
On Friday 02 March 2007, Michael Ellerman wrote: > There's also the error case for spu_run_init() which skips the master > stop. I guess that's ok because we've only set the master control in the > backing store, and the only way that will ever get propagated to an > actual spu is by coming back th

Re: [Cbe-oss-dev] [PATCH 14/22] spufs: use SPU master control to prevent wild SPU execution

2007-03-02 Thread Michael Ellerman
On Thu, 2007-03-01 at 14:50 +0100, Arnd Bergmann wrote: > On Thursday 01 March 2007, Michael Ellerman wrote: > > On Mon, 2006-11-20 at 18:45 +0100, Arnd Bergmann wrote: > > > plain text document attachment (spufs-master-control.diff) > > > When the user changes the runcontrol register, an SPU migh

Re: [Cbe-oss-dev] [PATCH 14/22] spufs: use SPU master control to prevent wild SPU execution

2007-03-01 Thread Arnd Bergmann
On Thursday 01 March 2007, Michael Ellerman wrote: > On Mon, 2006-11-20 at 18:45 +0100, Arnd Bergmann wrote: > > plain text document attachment (spufs-master-control.diff) > > When the user changes the runcontrol register, an SPU might be > > running without a process being attached to it and waiti

Re: [PATCH 14/22] spufs: use SPU master control to prevent wild SPU execution

2007-02-28 Thread Michael Ellerman
On Mon, 2006-11-20 at 18:45 +0100, Arnd Bergmann wrote: > plain text document attachment (spufs-master-control.diff) > When the user changes the runcontrol register, an SPU might be > running without a process being attached to it and waiting for > events. In order to prevent this, make sure we alw