From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: use a separate context for gpu relocs
Date: Mon, 26 Aug 2019 11:12:48 -0700 [thread overview]
Message-ID: <0e1a89c7-b9fc-c6c5-c588-7469ef55e142@intel.com> (raw)
In-Reply-To: <156684300251.15406.2123066162667016551@skylake-alporthouse-com>
On 8/26/19 11:10 AM, Chris Wilson wrote:
> Quoting Daniele Ceraolo Spurio (2019-08-26 18:56:53)
>>
>>
>> On 8/24/2019 1:54 AM, Chris Wilson wrote:
>>> Note that this requires us to fix the tagging so that we don't perform a
>>> lite-restore from the reloc instance to the user instance.
>>
>> What's wrong with lite-restoring in this case? It's not something we
>> stop now AFAICS.
>
> I have patches to fix the regression. But the question is whether or not
> the pre-parser is happy to cross the lite-restore boundary. If it is a
> light lite-restore and there is no cache invalidation...
> -Chris
>
On pre-gen12 the parser doesn't cross the BB_START, so we're safe from
that POV.
Daniele
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-26 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 0:20 [PATCH] drm/i915: use a separate context for gpu relocs Daniele Ceraolo Spurio
2019-08-24 0:32 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-08-24 1:25 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-08-24 8:54 ` [PATCH] " Chris Wilson
2019-08-26 17:56 ` Daniele Ceraolo Spurio
2019-08-26 18:10 ` Chris Wilson
2019-08-26 18:12 ` Daniele Ceraolo Spurio [this message]
2019-08-24 9:01 ` Chris Wilson
2019-08-24 9:03 ` 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=0e1a89c7-b9fc-c6c5-c588-7469ef55e142@intel.com \
--to=daniele.ceraolospurio@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