From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 9/9] drm/i915/selftests: mark up hugepages object with start_cpu_write
Date: Wed, 20 Oct 2021 17:12:00 +0200 [thread overview]
Message-ID: <aeed3c3a34fc08f0a6885a8c185b3517661a49f5.camel@linux.intel.com> (raw)
In-Reply-To: <20211018174508.2137279-9-matthew.auld@intel.com>
On Mon, 2021-10-18 at 18:45 +0100, Matthew Auld wrote:
> Just like we do for internal objects. Also just use
> i915_gem_object_set_cache_coherency() here. No need for over-flushing
> on
> LLC platforms.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gem/selftests/huge_pages.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Reivewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
WARNING: multiple messages have this Message-ID (diff)
From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 9/9] drm/i915/selftests: mark up hugepages object with start_cpu_write
Date: Wed, 20 Oct 2021 17:12:00 +0200 [thread overview]
Message-ID: <aeed3c3a34fc08f0a6885a8c185b3517661a49f5.camel@linux.intel.com> (raw)
In-Reply-To: <20211018174508.2137279-9-matthew.auld@intel.com>
On Mon, 2021-10-18 at 18:45 +0100, Matthew Auld wrote:
> Just like we do for internal objects. Also just use
> i915_gem_object_set_cache_coherency() here. No need for over-flushing
> on
> LLC platforms.
>
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gem/selftests/huge_pages.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Reivewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
next prev parent reply other threads:[~2021-10-20 15:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 17:45 [PATCH 1/9] drm/i915: mark dmabuf objects as ALLOC_USER Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-18 17:45 ` [PATCH 2/9] drm/i915: mark userptr " Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-20 14:36 ` Thomas Hellström
2021-10-20 14:36 ` [Intel-gfx] " Thomas Hellström
2021-10-18 17:45 ` [PATCH 3/9] drm/i915: extract bypass-llc check into helper Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-20 14:38 ` Thomas Hellström
2021-10-20 14:38 ` [Intel-gfx] " Thomas Hellström
2021-10-18 17:45 ` [Intel-gfx] [PATCH 4/9] drm/i915/dmabuf: add paranoid flush-on-acquire Matthew Auld
2021-10-18 17:45 ` Matthew Auld
2021-10-20 14:42 ` Thomas Hellström
2021-10-20 14:42 ` [Intel-gfx] " Thomas Hellström
2021-10-22 10:50 ` kernel test robot
2021-10-26 13:44 ` Guenter Roeck
2021-10-26 13:44 ` [Intel-gfx] " Guenter Roeck
2021-10-18 17:45 ` [PATCH 5/9] drm/i915/userptr: " Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-20 14:52 ` Thomas Hellström
2021-10-20 14:52 ` [Intel-gfx] " Thomas Hellström
2021-10-18 17:45 ` [PATCH 6/9] drm/i915/shmem: ensure flush during swap-in on non-LLC Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-20 14:53 ` Thomas Hellström
2021-10-20 14:53 ` [Intel-gfx] " Thomas Hellström
2021-10-18 17:45 ` [PATCH 7/9] drm/i915: expand on the kernel-doc for cache_dirty Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-20 14:58 ` Thomas Hellström
2021-10-20 14:58 ` [Intel-gfx] " Thomas Hellström
2021-10-18 17:45 ` [PATCH 8/9] drm/i915: mark up internal objects with start_cpu_write Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-20 15:11 ` Thomas Hellström
2021-10-20 15:11 ` [Intel-gfx] " Thomas Hellström
2021-10-18 17:45 ` [PATCH 9/9] drm/i915/selftests: mark up hugepages object " Matthew Auld
2021-10-18 17:45 ` [Intel-gfx] " Matthew Auld
2021-10-20 15:12 ` Thomas Hellström [this message]
2021-10-20 15:12 ` Thomas Hellström
2021-10-18 19:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/9] drm/i915: mark dmabuf objects as ALLOC_USER Patchwork
2021-10-18 19:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-10-18 19:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-10-19 2:39 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-10-20 14:34 ` [PATCH 1/9] " Thomas Hellström
2021-10-20 14:34 ` [Intel-gfx] " Thomas Hellström
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=aeed3c3a34fc08f0a6885a8c185b3517661a49f5.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.