>> While playing with GPU programming, I had a lot of such freeze, and they
>> never locked the CPU. I was always able to connect to my machine though SSH.
Sometimes you can, sometimes you can't. It depends on exactly how things fail.
> So a regular user process can permanently lock up the disp
On May 11, 2012, at 12:55 PM, Jens Alfke wrote:
> So a regular user process can permanently lock up the display, requiring a
> reboot, just by executing some bad GPU code?! That’s kind of a bad privilege
> violation and could be considered a DoS exploit.
On the old 2008 non-unibody MacBook Pro
Le 11 mai 2012 à 19:55, Jens Alfke a écrit :
>
> On May 11, 2012, at 9:23 AM, Jean-Daniel Dupas wrote:
>
>> While playing with GPU programming, I had a lot of such freeze, and they
>> never locked the CPU. I was always able to connect to my machine though SSH.
>
> So a regular user process ca
On May 11, 2012, at 9:23 AM, Jean-Daniel Dupas wrote:
> While playing with GPU programming, I had a lot of such freeze, and they
> never locked the CPU. I was always able to connect to my machine though SSH.
So a regular user process can permanently lock up the display, requiring a
reboot, jus
Le 11 mai 2012 à 18:05, Jens Alfke a écrit :
>
> On May 9, 2012, at 7:14 AM, Ph.T wrote:
>
>> . in a pre-emptive OS there should be no freezing;
>> given the new concurrency model
>> that includes the use of the graphics processor GPU
>> to do the system's non-graphics processing,
>
> Well, th
On May 9, 2012, at 7:14 AM, Ph.T wrote:
> . in a pre-emptive OS there should be no freezing;
> given the new concurrency model
> that includes the use of the graphics processor GPU
> to do the system's non-graphics processing,
Well, the GPU can _occasionally_ be used to do some non-graphics work
