From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/4] drm/i915: Flush all user surfaces prior to first use
Date: Fri, 19 Jul 2019 13:18:42 +0300 [thread overview]
Message-ID: <29f36349-0c1a-3af6-d707-632685f80929@intel.com> (raw)
In-Reply-To: <20190718145407.21352-3-chris@chris-wilson.co.uk>
On 18/07/2019 17:54, Chris Wilson wrote:
> Since userspace has the ability to bypass the CPU cache from within its
> unprivileged command stream, we have to flush the CPU cache to memory
> in order to overwrite the previous contents on creation.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: stablevger.kernel.org
> ---
> drivers/gpu/drm/i915/gem/i915_gem_shmem.c | 26 ++++++-----------------
> 1 file changed, 7 insertions(+), 19 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> index d2a1158868e7..f752b326d399 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gem_shmem.c
> @@ -459,7 +459,6 @@ i915_gem_object_create_shmem(struct drm_i915_private *i915, u64 size)
> {
> struct drm_i915_gem_object *obj;
> struct address_space *mapping;
> - unsigned int cache_level;
> gfp_t mask;
> int ret;
>
> @@ -498,24 +497,13 @@ i915_gem_object_create_shmem(struct drm_i915_private *i915, u64 size)
> obj->write_domain = I915_GEM_DOMAIN_CPU;
> obj->read_domains = I915_GEM_DOMAIN_CPU;
>
> - if (HAS_LLC(i915))
> - /* On some devices, we can have the GPU use the LLC (the CPU
> - * cache) for about a 10% performance improvement
> - * compared to uncached. Graphics requests other than
> - * display scanout are coherent with the CPU in
> - * accessing this cache. This means in this mode we
> - * don't need to clflush on the CPU side, and on the
> - * GPU side we only need to flush internal caches to
> - * get data visible to the CPU.
> - *
> - * However, we maintain the display planes as UC, and so
> - * need to rebind when first used as such.
> - */
> - cache_level = I915_CACHE_LLC;
> - else
> - cache_level = I915_CACHE_NONE;
> -
> - i915_gem_object_set_cache_coherency(obj, cache_level);
> + /*
> + * Note that userspace has control over cache-bypass
> + * via its command stream, so even on LLC architectures
> + * we have to flush out the CPU cache to memory to
> + * clear previous contents.
> + */
> + i915_gem_object_set_cache_coherency(obj, I915_CACHE_NONE);
>
> trace_i915_gem_object_create(obj);
>
Does i915_drm.h needs updating? :
/**
* I915_CACHING_CACHED
*
* GPU access is coherent with cpu caches and furthermore the data is
cached in
* last-level caches shared between cpu cores and the gpu GT. Default on
* machines with HAS_LLC.
*/
#define I915_CACHING_CACHED 1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-19 10:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 14:54 [PATCH 1/4] drm/i915: Drop wmb() inside pread_gtt Chris Wilson
2019-07-18 14:54 ` [PATCH 2/4] drm/i915: Use maximum write flush for pwrite_gtt Chris Wilson
2019-07-18 18:28 ` Ville Syrjälä
2019-07-18 19:19 ` Chris Wilson
2019-07-19 0:45 ` Sasha Levin
2019-07-18 14:54 ` [PATCH 3/4] drm/i915: Flush all user surfaces prior to first use Chris Wilson
2019-07-19 10:01 ` Joonas Lahtinen
2019-07-19 10:18 ` Lionel Landwerlin [this message]
2019-07-19 10:21 ` Chris Wilson
2019-07-19 22:55 ` Jason Ekstrand
2019-07-20 10:49 ` Chris Wilson
2019-07-24 20:37 ` Francisco Jerez
2019-11-12 9:38 ` Chris Wilson
2019-11-12 9:38 ` [Intel-gfx] " Chris Wilson
2019-11-12 19:58 ` Francisco Jerez
2019-11-12 19:58 ` [Intel-gfx] " Francisco Jerez
2019-07-18 14:54 ` [PATCH 4/4] drm/i915: Flush stale cachelines on set-cache-level Chris Wilson
2019-07-19 10:03 ` Joonas Lahtinen
2019-11-12 9:09 ` [Intel-gfx] " Daniel Vetter
2019-11-12 9:09 ` Daniel Vetter
2019-11-12 9:42 ` Chris Wilson
2019-11-12 9:42 ` Chris Wilson
2019-11-12 10:57 ` Daniel Vetter
2019-11-12 10:57 ` Daniel Vetter
2019-11-12 12:08 ` Daniel Vetter
2019-11-12 12:08 ` Daniel Vetter
2019-07-18 15:35 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915: Drop wmb() inside pread_gtt Patchwork
2019-07-18 16:22 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-18 17:29 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-18 18:23 ` [PATCH 1/4] " Ville Syrjälä
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=29f36349-0c1a-3af6-d707-632685f80929@intel.com \
--to=lionel.g.landwerlin@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