On Mon, 28 Mar 2011 15:37:37 -0700, Ben Widawsky <[email protected]> wrote: > On Mon, Mar 28, 2011 at 10:55:40AM -0700, Eric Anholt wrote: > > --- > > I suspect due to > > FORCEWAKE, which also means that I can't necessarily trust that the > > bit was unset originally), I got only hangs from 3D. > > If you want to get some more possibly garbage data, you can set > forcewake from userspace, and hope the kernel doesn't unset it :). > > intel_reg_write 0xa18c 1 > # check for ack > intel_reg_read 0x130090 > > I've never tried it, but it might work at least for reading that first > bit. I'm currenty working around this with > <[email protected]> > and a hack in the kernel to do a get() and never do a put.
I'm tempted by the idea of having a kernel interface for unpriveleged interfaces for reading these regs, which would allow for non-root gpu_top in addition to doing the forcewake. It'll suck to maintain a list of unpriveleged-OK regs, though.
pgpNdsRbrNP28.pgp
Description: PGP signature
_______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
