Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Vikas Srivastava <vikas.srivastava@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v4] tests/i915: skip gem_set_caching call for mtl
Date: Wed, 05 Apr 2023 22:24:34 -0700	[thread overview]
Message-ID: <87pm8hoa5p.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230331124717.3005947-1-vikas.srivastava@intel.com>

On Fri, 31 Mar 2023 05:47:17 -0700, Vikas Srivastava wrote:
>
> diff --git a/lib/ioctl_wrappers.c b/lib/ioctl_wrappers.c
> index 1ab41ab6d6..ebd8a2f36f 100644
> --- a/lib/ioctl_wrappers.c
> +++ b/lib/ioctl_wrappers.c
> @@ -1297,3 +1297,17 @@ bool igt_has_drm_cap(int fd, uint64_t capability)
>	igt_assert(drmIoctl(fd, DRM_IOCTL_GET_CAP, &cap) == 0);
>	return cap.value;
>  }
> +
> +/**
> + * igt_has_set_caching:
> + * @devid: platform id.
> + *
> + * This helper verifies if the passed platform id
> + * has support for setting cache.
> + *
> + * Returns: Whether the cache setting  is supported or not.
> + */
> +bool igt_has_set_caching(uint32_t devid)
> +{
> +	return IS_METEORLAKE(devid) ? false : true;

Can we include the gem_has_lmem condition below here too?


> +}
> diff --git a/lib/ioctl_wrappers.h b/lib/ioctl_wrappers.h
> index e4d7c0d408..4c232078d0 100644
> --- a/lib/ioctl_wrappers.h
> +++ b/lib/ioctl_wrappers.h
> @@ -145,6 +145,7 @@ void prime_sync_end(int dma_buf_fd, bool write);
>  bool igt_has_fb_modifiers(int fd);
>  void igt_require_fb_modifiers(int fd);
>  bool igt_has_drm_cap(int fd, uint64_t capability);
> +bool igt_has_set_caching(uint32_t devid);
>
>  /**
>   * __kms_addfb:
> diff --git a/tests/i915/gem_caching.c b/tests/i915/gem_caching.c
> index eb0170abca..d0c7aa035f 100644
> --- a/tests/i915/gem_caching.c
> +++ b/tests/i915/gem_caching.c
> @@ -158,6 +158,11 @@ igt_main
>			igt_info("coherency broken on i965g/gm\n");
>			flags = 0;
>		}
> +
> +		if (!gem_has_lmem(data.fd))
> +			igt_require_f(igt_has_set_caching(data.devid),
> +				      " cache setting not supported on this target\n");
> +
>		data.bops = buf_ops_create(data.fd);
>
>		scratch_buf = intel_buf_create(data.bops, BO_SIZE/4, 1,

      parent reply	other threads:[~2023-04-06  5:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 12:47 [igt-dev] [PATCH i-g-t v4] tests/i915: skip gem_set_caching call for mtl Vikas Srivastava
2023-03-31 15:36 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915: skip gem_set_caching call for mtl (rev6) Patchwork
2023-04-01 14:34 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-04-04  8:24 ` [igt-dev] [PATCH i-g-t v4] tests/i915: skip gem_set_caching call for mtl Kamil Konieczny
2023-04-06  5:24 ` Dixit, Ashutosh [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=87pm8hoa5p.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=vikas.srivastava@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