From: Michel Thierry <michel.thierry@intel.com>
To: "Chris Wilson" <chris@chris-wilson.co.uk>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/ppgtt: Load address space after mi_set_context
Date: Fri, 12 Sep 2014 17:56:30 +0100 [thread overview]
Message-ID: <541325BE.5080302@intel.com> (raw)
In-Reply-To: <20140912154047.GJ16043@nuc-i3427.alporthouse.com>
On 9/12/2014 4:40 PM, Chris Wilson wrote:
> On Fri, Sep 12, 2014 at 06:35:10PM +0300, Ville Syrjälä wrote:
>> On Fri, Sep 12, 2014 at 04:10:01PM +0100, Michel Thierry wrote:
>>> From: Ben Widawsky <benjamin.widawsky@intel.com>
>>>
>>> The simple explanation is, the docs say to do this for GEN8. Perhaps we
>>> want to do this for GEN7 too, I am not certain.
>>>
>>> PDPs are saved and restored with context. Contexts (without execlists)
>>> only exist on the render ring. The docs say that PDPs are not power
>>> context save/restored. I've learned that this actually means something
>>> which SW doesn't care about. So pretend the statement doesn't exist.
>>> For non RCS, nothing changes.
>
> Hang on. This is exactly what I was worried about... Which PDPs are
> saved with context? Why doesn't this mean that we aren't overwitting
> PDPs in use on other rings when RCS loads a new context?
> -Chris
>
I was wondering the same when I read Ben's original comment. Could this
be GEN8 specific?
next prev parent reply other threads:[~2014-09-12 16:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 15:10 [PATCH] drm/i915/ppgtt: Load address space after mi_set_context Michel Thierry
2014-09-12 15:35 ` Ville Syrjälä
2014-09-12 15:40 ` Chris Wilson
2014-09-12 16:56 ` Michel Thierry [this message]
2014-09-12 17:14 ` Ville Syrjälä
2014-09-15 9:29 ` [PATCH v4] " Michel Thierry
2014-09-15 9:42 ` Chris Wilson
[not found] ` <54211877.5070401@intel.com>
2014-09-23 6:58 ` Zhi Wang
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=541325BE.5080302@intel.com \
--to=michel.thierry@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.intel.com \
/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