From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: HSW always use GGTT selector for secure batches
Date: Wed, 10 Sep 2014 15:00:03 +0300 [thread overview]
Message-ID: <20140910120003.GR4193@intel.com> (raw)
In-Reply-To: <20140910112143.GB31074@nuc-i3427.alporthouse.com>
On Wed, Sep 10, 2014 at 12:21:43PM +0100, Chris Wilson wrote:
> On Wed, Sep 10, 2014 at 12:18:27PM +0100, Chris Wilson wrote:
> > gen6 and earlier conflate address space selection (ppgtt vs ggtt) with
> > the security bit (i.e. only privileged batches were allowed to run from
> > ggtt). From Haswell onwards, you are able to select the security bit
>
> ggtt). For Haswell only, you are able to select the security bit
>
> > separate from the address space - and we always requested to use ppgtt.
> > This breaks the golden render state batch execution with full-ppgtt as
> > that is only present in the global GTT and more generally any secure
> > batch that is not colocated in the ppgtt and ggtt. So we need to
> > disable the use of the ppgtt selector bit for secure batches, or else we
> > hang immediately upon boot and thence after every GPU reset...
> >
> > v2: Only HSW differentiates between secure dispatch and ggtt, so simply
> > ignore the differentiation and always use secure==ggtt.
> >
> > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_ringbuffer.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index 109de2eeb9a8..25795f2efdcb 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -2203,8 +2203,9 @@ hsw_ring_dispatch_execbuffer(struct intel_engine_cs *ring,
> > return ret;
> >
> > intel_ring_emit(ring,
> > - MI_BATCH_BUFFER_START | MI_BATCH_PPGTT_HSW |
> > - (flags & I915_DISPATCH_SECURE ? 0 : MI_BATCH_NON_SECURE_HSW));
> > + MI_BATCH_BUFFER_START |
> > + (flags & I915_DISPATCH_SECURE ?
> > + 0 : MI_BATCH_PPGTT_HSW | MI_BATCH_NON_SECURE_HSW));
> > /* bit0-7 is the length on GEN6+ */
> > intel_ring_emit(ring, offset);
> > intel_ring_advance(ring);
> > --
> > 2.1.0
> >
>
> --
> Chris Wilson, Intel Open Source Technology Centre
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-09-10 12:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 9:26 [PATCH] drm/i915: Use GGTT batchbuffer selector Chris Wilson
2014-09-10 9:46 ` Chris Wilson
2014-09-10 10:30 ` Ville Syrjälä
2014-09-10 10:50 ` Chris Wilson
2014-09-10 11:18 ` [PATCH] drm/i915: HSW always use GGTT selector for secure batches Chris Wilson
2014-09-10 11:21 ` Chris Wilson
2014-09-10 12:00 ` Ville Syrjälä [this message]
2014-09-10 12:16 ` Daniel Vetter
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=20140910120003.GR4193@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=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