From: Matthew Auld <matthew.auld@intel.com>
To: Sanjay Yadav <sanjay.kumar.yadav@intel.com>,
intel-xe@lists.freedesktop.org
Cc: "José Roberto de Souza" <jose.souza@intel.com>,
"Stuart Summers" <stuart.summers@intel.com>
Subject: Re: [PATCH] drm/xe/query: Only advertise NO_COMPRESSION hint on devices with flat CCS
Date: Thu, 5 Feb 2026 09:56:20 +0000 [thread overview]
Message-ID: <baaa9fe2-5fa5-47da-a5f4-4647d0d431af@intel.com> (raw)
In-Reply-To: <20260205082048.2988738-2-sanjay.kumar.yadav@intel.com>
On 05/02/2026 08:20, Sanjay Yadav wrote:
> Devices like CRI have GRAPHICS_VER >= 20 but don't have compression
> support their PAT table (xe3p_xpc_pat_table) has no compression-enabled
> entries.
>
> Only advertise HAS_NO_COMPRESSION_HINT flag when the device actually has
> flat CCS and thus compression capability.
>
> Fixes: 78d91ba6bd796 ("drm/xe/uapi: Add NO_COMPRESSION BO flag and query capability")
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: José Roberto de Souza <jose.souza@intel.com>
> Cc: Stuart Summers <stuart.summers@intel.com>
> Signed-off-by: Sanjay Yadav <sanjay.kumar.yadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_query.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_query.c b/drivers/gpu/drm/xe/xe_query.c
> index 34db266b723f..c152ebfbd7d8 100644
> --- a/drivers/gpu/drm/xe/xe_query.c
> +++ b/drivers/gpu/drm/xe/xe_query.c
> @@ -335,7 +335,7 @@ static int query_config(struct xe_device *xe, struct drm_xe_device_query *query)
> if (xe->info.has_usm && IS_ENABLED(CONFIG_DRM_XE_GPUSVM))
> config->info[DRM_XE_QUERY_CONFIG_FLAGS] |=
> DRM_XE_QUERY_CONFIG_FLAG_HAS_CPU_ADDR_MIRROR;
> - if (GRAPHICS_VER(xe) >= 20)
> + if (GRAPHICS_VER(xe) >= 20 && xe_device_has_flat_ccs(xe))
I think we need to also update the check in bo_create() to match this?
If we claim the flag is not supported, then using the flag should be
rejected, I think. The IGT for this will fail otherwise?
> config->info[DRM_XE_QUERY_CONFIG_FLAGS] |=
> DRM_XE_QUERY_CONFIG_FLAG_HAS_NO_COMPRESSION_HINT;
> config->info[DRM_XE_QUERY_CONFIG_FLAGS] |=
next prev parent reply other threads:[~2026-02-05 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 8:20 [PATCH] drm/xe/query: Only advertise NO_COMPRESSION hint on devices with flat CCS Sanjay Yadav
2026-02-05 8:31 ` ✓ CI.KUnit: success for " Patchwork
2026-02-05 9:29 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-05 9:39 ` [PATCH] " Vivekanandan, Balasubramani
2026-02-05 9:49 ` Matthew Auld
2026-02-05 9:56 ` Matthew Auld [this message]
2026-02-05 13:43 ` Souza, Jose
2026-02-05 14:17 ` Matthew Auld
2026-02-06 13:28 ` Souza, Jose
2026-02-06 4:33 ` ✓ Xe.CI.FULL: success for " 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=baaa9fe2-5fa5-47da-a5f4-4647d0d431af@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=sanjay.kumar.yadav@intel.com \
--cc=stuart.summers@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.