From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
dri-devel@lists.freedesktop.org,
"Chris Wilson" <chris@chris-wilson.co.uk>
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/gtt: stop caching the scratch page
Date: Mon, 22 Nov 2021 09:43:15 +0000 [thread overview]
Message-ID: <4d5deeb3-1eb9-f374-6729-1fe03d5e774e@linux.intel.com> (raw)
In-Reply-To: <20211028092638.3142258-2-matthew.auld@intel.com>
On 28/10/2021 10:26, Matthew Auld wrote:
> Normal users shouldn't be hitting this, likely this would indicate a
> userspace bug. So don't bother caching, which should be safe now that we
> manually flush the page.
Could this have a performance impact if "things" overfetch often enough
in normal operation?
Regards,
Tvrtko
> Suggested-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Ramalingam C <ramalingam.c@intel.com>
> Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gt/gen8_ppgtt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/gen8_ppgtt.c b/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> index 8af2f709571c..9966e9dc5218 100644
> --- a/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> +++ b/drivers/gpu/drm/i915/gt/gen8_ppgtt.c
> @@ -651,7 +651,7 @@ static int gen8_init_scratch(struct i915_address_space *vm)
>
> vm->scratch[0]->encode =
> gen8_pte_encode(px_dma(vm->scratch[0]),
> - I915_CACHE_LLC, pte_flags);
> + I915_CACHE_NONE, pte_flags);
>
> for (i = 1; i <= vm->top; i++) {
> struct drm_i915_gem_object *obj;
> @@ -667,7 +667,7 @@ static int gen8_init_scratch(struct i915_address_space *vm)
> }
>
> fill_px(obj, vm->scratch[i - 1]->encode);
> - obj->encode = gen8_pde_encode(px_dma(obj), I915_CACHE_LLC);
> + obj->encode = gen8_pde_encode(px_dma(obj), I915_CACHE_NONE);
>
> vm->scratch[i] = obj;
> }
>
next prev parent reply other threads:[~2021-11-22 9:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 9:26 [Intel-gfx] [PATCH v2 1/2] drm/i915/gtt: flush the scratch page Matthew Auld
2021-10-28 9:26 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/gtt: stop caching " Matthew Auld
2021-11-22 9:43 ` Tvrtko Ursulin [this message]
2021-10-28 14:46 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v2,1/2] drm/i915/gtt: flush " Patchwork
2021-10-28 18:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=4d5deeb3-1eb9-f374-6729-1fe03d5e774e@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=thomas.hellstrom@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