public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Set DERRMR around batches required vblank events
Date: Wed, 29 Aug 2012 16:33:13 +0100	[thread overview]
Message-ID: <84c8a8$5i2r5r@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1343334619-28340-1-git-send-email-chris@chris-wilson.co.uk>

On Thu, 26 Jul 2012 21:30:19 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> In order for the Display Engine to send messages to the Render Engine,
> that event must be unmasked in the Display Engine Render Response Mask
> Register (DERRMR). By default all events are masked to prevent unwanted
> messages to conserve power, and it is strongly recommended that only
> single events be unmasked at any time. So in order to pipeline the
> register writes around individual batchbuffers, userspace must notify
> the kernel when it requires a vblank event, this patch implements an
> interface to do so with an single (pipe, event) request through the
> execbuffer flags.
> 
> Note that another workaround is required for IVB, in that we must also
> prevent RC6 sleeps whilst waiting upon an event. To do that we also
> pipeline a forcewake into the second MT slot.

Anyone have any criticisms for this patch?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-08-29 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 20:30 [PATCH] drm/i915: Set DERRMR around batches required vblank events Chris Wilson
2012-08-29 15:33 ` Chris Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-16  9:47 Chris Wilson
2012-10-16 14:15 ` Daniel Vetter
2012-10-17 13:58   ` 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='84c8a8$5i2r5r@orsmga001.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox