public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Document the multi-threaded FORCEWAKE bits
Date: Wed, 17 Oct 2012 21:10:40 +0200	[thread overview]
Message-ID: <20121017191040.GO5753@phenom.ffwll.local> (raw)
In-Reply-To: <20121017100515.239e7eec@jbarnes-desktop>

On Wed, Oct 17, 2012 at 10:05:15AM -0700, Jesse Barnes wrote:
> On Wed, 17 Oct 2012 09:27:24 -0700
> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> 
> > On Wed, 17 Oct 2012 12:09:55 +0100
> > Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > 
> > > No functional change, but reserves 0x2 for use by userspace.
> > > 
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > > ---
> > >  drivers/gpu/drm/i915/i915_reg.h |    2 ++
> > >  drivers/gpu/drm/i915/intel_pm.c |   10 +++++-----
> > >  2 files changed, 7 insertions(+), 5 deletions(-)
> > 
> > Each of the bits in this reg correspond to a specific agent that may
> > need to wake the GT.  Unfortunately I don't have docs about which bits
> > are used by which agents.  IIRC the BIOS uses one as does the AMT
> > engine if present.
> > 
> > I'll try to find out who owns each and maybe we can reserve our own for
> > userspace.
> 
> Ok we're in the clear here.  I was afraid there might be other system
> components that would do sneaky things behind our back.  But once the
> driver loads, we own the GT, so we can make these bits whatever we want.

I guess that counts for an ack - patch merged to dinq.

Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2012-10-17 19:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16  9:47 [PATCH] drm/i915: Set DERRMR around batches required vblank events Chris Wilson
2012-10-16 14:15 ` Daniel Vetter
2012-10-17 11:09   ` [PATCH 1/2] drm/i915: Allow DRM_ROOT_ONLY|DRM_MASTER to submit privileged batchbuffers Chris Wilson
2012-10-17 11:09     ` [PATCH 2/2] drm/i915: Document the multi-threaded FORCEWAKE bits Chris Wilson
2012-10-17 16:27       ` Jesse Barnes
2012-10-17 17:05         ` Jesse Barnes
2012-10-17 19:10           ` Daniel Vetter [this message]
2012-10-17 16:31     ` [PATCH 1/2] drm/i915: Allow DRM_ROOT_ONLY|DRM_MASTER to submit privileged batchbuffers Jesse Barnes
2012-10-17 19:09       ` Daniel Vetter
2012-10-17 18:47     ` Eric Anholt
2012-10-17 19:04       ` Daniel Vetter
2012-10-17 13:58   ` [PATCH] drm/i915: Set DERRMR around batches required vblank events 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=20121017191040.GO5753@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox