On Thu, Aug 14, 2014 at 01:18:46PM +0300, Mika Kuoppala wrote:
> Chris Wilson writes:
>
> > On Wed, Aug 13, 2014 at 05:50:38PM +0300, Mika Kuoppala wrote:
> >> Chris Wilson writes:
> >>
> >> > The current error state harks back to the era of just a single VM. For
> >> > full-ppgtt, we capture e
Chris Wilson writes:
> On Wed, Aug 13, 2014 at 05:50:38PM +0300, Mika Kuoppala wrote:
>> Chris Wilson writes:
>>
>> > The current error state harks back to the era of just a single VM. For
>> > full-ppgtt, we capture every bo on every VM. It behoves us to then print
>> > every bo for every VM,
On Wed, Aug 13, 2014 at 05:50:38PM +0300, Mika Kuoppala wrote:
> Chris Wilson writes:
>
> > The current error state harks back to the era of just a single VM. For
> > full-ppgtt, we capture every bo on every VM. It behoves us to then print
> > every bo for every VM, which we currently fail to do
Chris Wilson writes:
> The current error state harks back to the era of just a single VM. For
> full-ppgtt, we capture every bo on every VM. It behoves us to then print
> every bo for every VM, which we currently fail to do and so miss vital
> information in the error state.
>
> v2: Use the vma a
The current error state harks back to the era of just a single VM. For
full-ppgtt, we capture every bo on every VM. It behoves us to then print
every bo for every VM, which we currently fail to do and so miss vital
information in the error state.
v2: Use the vma address rather than -1!
Signed-off
