From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <ben@bwidawsk.net>, intel-gfx@lists.freedesktop.org
Subject: Re: enabling forcewake from userspace
Date: Sat, 26 Mar 2011 07:11:55 +0000 [thread overview]
Message-ID: <b9dded$iefp22@orsmga002.jf.intel.com> (raw)
In-Reply-To: <20110326022358.GA24223@lundgren.kumite>
On Fri, 25 Mar 2011 19:23:58 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> The only other option floating around is IOCTLs to read/write the
> registers, which previously seemed like a bad idea, but is now looking
> like the only option.
The lazy option is to cross your fingers and do the forced-wake from
userspace debug tools. I'm not exactly wild about the idea, but it does
cut down on the number of blessed interfaces for touching hardware.
The other option is to continue to extend the debugfs to print out groups
of registers of interest. Maybe this would be a good addition to the
i915_*_ringbuffer_info?
An ioctl does seem to be a better longterm solution. But maybe we can
ignore the problem for a few more years? ;-)
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-03-26 7:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-26 2:07 enabling forcewake from userspace Ben Widawsky
2011-03-26 2:07 ` [PATCH] drm/i915: have a forcewake "refcount" Ben Widawsky
2011-03-26 2:23 ` enabling forcewake from userspace Ben Widawsky
2011-03-26 7:11 ` Chris Wilson [this message]
2011-03-26 15:46 ` Ben Widawsky
2011-03-26 17:18 ` Chris Wilson
2011-03-26 19:27 ` Ben Widawsky
2011-03-26 20:20 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='b9dded$iefp22@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.