From: Daniel Vetter <daniel@ffwll.ch>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Do not access stolen memory directly by the CPU, even for error capture
Date: Tue, 15 Jul 2014 16:15:08 +0200 [thread overview]
Message-ID: <20140715141508.GW15237@phenom.ffwll.local> (raw)
In-Reply-To: <20140424214748.GA23141@bwidawsk.net>
On Thu, Apr 24, 2014 at 02:47:48PM -0700, Ben Widawsky wrote:
> On Wed, Feb 12, 2014 at 07:18:40PM +0000, Chris Wilson wrote:
> > For stolen pages, since it is verboten to access them directly on many
> > architectures, we have to read them through the GTT aperture. If they
> > are not accessible through the aperture, then we have to abort.
> >
> > This was complicated by
> >
> > commit 8b6124a633d8095b0c8364f585edff9c59568a96
> > Author: Chris Wilson <chris@chris-wilson.co.uk>
> > Date: Thu Jan 30 14:38:16 2014 +0000
> >
> > drm/i915: Don't access snooped pages through the GTT (even for error capture)
> >
> > and the desire to use stolen memory for ringbuffers, contexts and
> > batches in the future.
>
> I am somewhat unclear as to whether we want to prefer the aperture for
> reading back objects which may be mapped in multiple address spaces.
Is there a polished version of this floating somewhere which I've missed?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-07-15 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 19:18 [PATCH] drm/i915: Do not access stolen memory directly by the CPU, even for error capture Chris Wilson
2014-02-18 19:18 ` Ben Widawsky
2014-03-04 14:45 ` Daniel Vetter
2014-03-04 21:27 ` Ben Widawsky
2014-03-04 22:01 ` Chris Wilson
2014-03-05 9:18 ` Chris Wilson
2014-04-24 21:47 ` Ben Widawsky
2014-07-15 14:15 ` Daniel Vetter [this message]
2014-07-16 3:30 ` Ben Widawsky
2014-07-20 8:29 ` Chris Wilson
2014-07-20 18:59 ` Ben Widawsky
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=20140715141508.GW15237@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox