From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH] drm/i915: Fix secure dispatch with full ppgtt
Date: Mon, 11 Aug 2014 13:22:19 +0200 [thread overview]
Message-ID: <20140811112219.GJ8727@phenom.ffwll.local> (raw)
In-Reply-To: <20140811101740.GF6666@nuc-i3427.alporthouse.com>
On Mon, Aug 11, 2014 at 11:17:40AM +0100, Chris Wilson wrote:
> On Mon, Aug 11, 2014 at 12:08:58PM +0200, Daniel Vetter wrote:
> > Based upon a hunk from a patch from Chris Wilson, but augmented to:
> > - Process the batch in the full ppgtt vm so that self-relocations
> > match again with userspace's expectations..
> > - Add a comment why plain pin for the global gtt binding is safe at
> > that point.
> >
> > v2: Drop local bind_vm variable (Chris).
> >
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Cc: Ben Widawsky <benjamin.widawsky@intel.com>
> > Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>
> /me jaw drops
>
> Oh nice, yes you are right that does fix the issue with the relocations
> being in one address space whilst the exec needs to be done from gGTT.
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Actually it's not that simple - with this patch we don't add the ggtt vma
for the batch to the active list, which we probably should. So needs to be
revised a bit more I think ...
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-08-11 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-11 10:05 [PATCH] drm/i915: Fix secure dispatch with full ppgtt Daniel Vetter
2014-08-11 10:08 ` Daniel Vetter
2014-08-11 10:17 ` Chris Wilson
2014-08-11 11:22 ` Daniel Vetter [this message]
2014-08-11 11:35 ` Chris Wilson
2014-08-11 11:51 ` 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=20140811112219.GJ8727@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=benjamin.widawsky@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--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