Re: [Nouveau] Documentation request for MP warp error 0x10

On Fri, Nov 6, 2015 at 4:19 PM, Robert Morell wrote: > On Fri, Nov 06, 2015 at 04:15:29PM -0500, Ilia Mirkin wrote: >> In order for ATOM.*/RED.* to work, the addresses in question must >> *NOT* be inside of the 16MB local/shared windows. So if I'm getting >> that error, the

Re: [Nouveau] Documentation request for MP warp error 0x10

On Fri, Oct 02, 2015 at 06:05:21PM -0400, Ilia Mirkin wrote: > Could you advise what the proper way of indicating > that the memory is "global" to the op? I'm sure I'm just missing > something simple. If you show me what to look for in SM35 I can > probably find it on my own for SM20/SM30/SM50.

Re: [Nouveau] Documentation request for MP warp error 0x10

On Fri, Nov 6, 2015 at 3:59 PM, Robert Morell wrote: > On Fri, Oct 02, 2015 at 06:05:21PM -0400, Ilia Mirkin wrote: >> Could you advise what the proper way of indicating >> that the memory is "global" to the op? I'm sure I'm just missing >> something simple. If you show me

Re: [Nouveau] Documentation request for MP warp error 0x10

On Fri, Nov 06, 2015 at 04:15:29PM -0500, Ilia Mirkin wrote: > In order for ATOM.*/RED.* to work, the addresses in question must > *NOT* be inside of the 16MB local/shared windows. So if I'm getting > that error, the address must be inside. Yes, that's my understanding. > If so, this may be a

Re: [Nouveau] Documentation request for MP warp error 0x10

On Mon, Oct 26, 2015 at 03:28:59PM -0400, Ilia Mirkin wrote: > On Fri, Oct 2, 2015 at 6:14 PM, Robert Morell wrote: > > Hi Ilia, > > > > On Fri, Oct 02, 2015 at 06:05:21PM -0400, Ilia Mirkin wrote: > >> Hi Robert, > >> > >> Thanks for the quick response! That goes in line with

Re: [Nouveau] Documentation request for MP warp error 0x10

On Fri, Oct 2, 2015 at 6:14 PM, Robert Morell wrote: > Hi Ilia, > > On Fri, Oct 02, 2015 at 06:05:21PM -0400, Ilia Mirkin wrote: >> Hi Robert, >> >> Thanks for the quick response! That goes in line with my observations >> which is that these things happen when using an

Re: [Nouveau] Documentation request for MP warp error 0x10

Hi Ilia, Error 0x10 is INVALID_ADDR_SPACE. It is triggered when an ATOM or RED [1] instruction accesses local or shared memory. Global memory accesses are the only allowed accesses for ATOM and RED instructions. Note that SM30 also has this restriction that ATOM and RED should only be used on

Re: [Nouveau] Documentation request for MP warp error 0x10

Hi Robert, Thanks for the quick response! That goes in line with my observations which is that these things happen when using an ATOM/RED instruction. I've checked and rechecked that I'm generating ops with identical bits as what the proprietary driver does, however (and nvdisasm prints identical

Re: [Nouveau] Documentation request for MP warp error 0x10

Hi Ilia, On Fri, Oct 02, 2015 at 06:05:21PM -0400, Ilia Mirkin wrote: > Hi Robert, > > Thanks for the quick response! That goes in line with my observations > which is that these things happen when using an ATOM/RED instruction. > I've checked and rechecked that I'm generating ops with identical

[Nouveau] Documentation request for MP warp error 0x10

Hello, I've recently come across an error reported by the GPU and would like to know what it means and especially what causes it to be triggered. Any information would be very useful: I'm seeing MP warp error 0x10 (appears in MP register 0x48). This is what we currently have in nouveau: