On Sat, Dec 14, 2013 at 05:48:08PM -0800, Ben Widawsky wrote:
> On Sat, Dec 14, 2013 at 09:38:57PM +, Chris Wilson wrote:
> > Capturing the semaphore_obj itself looks a bit silly since we never do
> > dump it into i915_error_state, but I actually like how you've reading back
> > of
> > the sem
On Sat, Dec 14, 2013 at 09:38:57PM +, Chris Wilson wrote:
> On Sat, Dec 14, 2013 at 11:47:24AM -0800, Ben Widawsky wrote:
> > On Fri, Dec 13, 2013 at 08:16:03PM -0800, Ben Widawsky wrote:
> > > Since the semaphore information is in an object, just dump it, and let
> > > the user parse it later.
On Sat, Dec 14, 2013 at 11:47:24AM -0800, Ben Widawsky wrote:
> On Fri, Dec 13, 2013 at 08:16:03PM -0800, Ben Widawsky wrote:
> > Since the semaphore information is in an object, just dump it, and let
> > the user parse it later.
> >
> > NOTE: The page being used for the semaphores are incoherent
On Fri, Dec 13, 2013 at 08:16:03PM -0800, Ben Widawsky wrote:
> Since the semaphore information is in an object, just dump it, and let
> the user parse it later.
>
> NOTE: The page being used for the semaphores are incoherent with the
> CPU. No matter what I do, I cannot figure out a way to read a
Since the semaphore information is in an object, just dump it, and let
the user parse it later.
NOTE: The page being used for the semaphores are incoherent with the
CPU. No matter what I do, I cannot figure out a way to read anything but
0s. Note that the semaphore waits are indeed working.
Signe
