From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, igt-dev@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t 1/2] tests/i915/gem_caching: handle discrete
Date: Wed, 4 May 2022 17:22:06 +0200 [thread overview]
Message-ID: <85639b1a-f85e-cf26-42d5-8ce868a494a4@linux.intel.com> (raw)
In-Reply-To: <20220504150845.158789-1-matthew.auld@intel.com>
The series is Reviewed-by: Nirmoy Das <nirmoy.das@intel.com>
On 5/4/2022 5:08 PM, Matthew Auld wrote:
> Test should still be valid, even if we can't explicitly control the PTE
> caching bits, like on discrete, where the caching should already be
> enabled by default for system memory objects.
>
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/4873
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Nirmoy Das <nirmoy.das@linux.intel.com>
> ---
> tests/i915/gem_caching.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/tests/i915/gem_caching.c b/tests/i915/gem_caching.c
> index 4e844952..eb0170ab 100644
> --- a/tests/i915/gem_caching.c
> +++ b/tests/i915/gem_caching.c
> @@ -147,7 +147,8 @@ igt_main
>
> igt_require_gem(data.fd);
> gem_require_blitter(data.fd);
> - gem_require_caching(data.fd);
> + if (!gem_has_lmem(data.fd))
> + gem_require_caching(data.fd);
>
> data.devid = intel_get_drm_devid(data.fd);
> if (IS_GEN2(data.devid)) /* chipset only handles cached -> uncached */
> @@ -162,7 +163,8 @@ igt_main
> scratch_buf = intel_buf_create(data.bops, BO_SIZE/4, 1,
> 32, 0, I915_TILING_NONE, 0);
>
> - gem_set_caching(data.fd, scratch_buf->handle, 1);
> + if (!gem_has_lmem(data.fd))
> + gem_set_caching(data.fd, scratch_buf->handle, 1);
>
> staging_buf = intel_buf_create(data.bops, BO_SIZE/4, 1,
> 32, 0, I915_TILING_NONE, 0);
prev parent reply other threads:[~2022-05-04 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 15:08 [Intel-gfx] [PATCH i-g-t 1/2] tests/i915/gem_caching: handle discrete Matthew Auld
2022-05-04 15:08 ` [Intel-gfx] [PATCH i-g-t 2/2] tests/i915/gem_workarounds: " Matthew Auld
2022-05-04 15:22 ` Das, Nirmoy [this message]
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=85639b1a-f85e-cf26-42d5-8ce868a494a4@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=igt-dev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox