[Nouveau] Documentation request for MP warp error 0x10

[Robert Morell]

On Mon, Oct 26, 2015 at 03:28:59PM -0400, Ilia Mirkin wrote:
> On Fri, Oct 2, 2015 at 6:14 PM, Robert Morell <rmorell at nvidia.com> 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 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 output). 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.
> >
> > Unfortunately this isn't something I know a lot about, so I'm going to
> > have do some research and get back to you, hopefully within a few days.
> 
> Hi Robert,
> 
> Were you able to find any further information out about this? Happy to
> provide with any traces or additional details as to what I'm doing
> (and which is failing).

I'm still waiting for clarification on some stuff I'm not sure about --
I'll try pinging a little harder.

Sorry for the delay.

- Robert