On Mon, Feb 27, 2017 at 06:34:26PM +0200, Jani Nikula wrote: > On Thu, 23 Feb 2017, Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> wrote: > > After initiating a sideband transaction, we only want to wait for the > > transaction to become idle. If, as we are, we wait for both the busy > > and error flag to clear, if an error is raised we just spin until the > > timeout. Once the hw is idle, we can then check to see if the hw flagged > > an error, and report it distinctly. > > > > Signed-off-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > > Cc: Jani Nikula <jani.nikula@xxxxxxxxx> > > Much better indeed. > > Reviewed-by: Jani Nikula <jani.nikula@xxxxxxxxx> > > (The pedantic nitpick is that response status is really two bits, and > you could read them both and fail if they're not zero. But meh.) First goal is just figuring out what the warnings mean on the gvtg machines. :) -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
