From: "Jahagirdar, Akshata" <akshata.jahagirdar@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v1 1/3] drm-uapi/xe_drm: Read flat ccs value from drm_xe_query_config
Date: Mon, 25 Mar 2024 22:29:26 -0700 [thread overview]
Message-ID: <3b2f7338-195e-4410-b662-290550587a3b@intel.com> (raw)
In-Reply-To: <20240326051937.d62ix7ni6sbbdbjx@zkempczy-mobl2>
On 3/25/2024 10:19 PM, Zbigniew Kempczyński wrote:
> On Tue, Mar 26, 2024 at 02:54:36AM -0700, Akshata Jahagirdar wrote:
>> Add an additional drm_xe_query_config_flag for reading the value
>> of flat_ccs of the platform.
>> This can be used in respective igt testcases.
>>
>> Signed-off-by: Akshata Jahagirdar <akshata.jahagirdar@intel.com>
>> ---
>> include/drm-uapi/xe_drm.h | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
>> index 4353595a4..b43c8cf76 100644
>> --- a/include/drm-uapi/xe_drm.h
>> +++ b/include/drm-uapi/xe_drm.h
>> @@ -389,6 +389,8 @@ struct drm_xe_query_mem_regions {
>> *
>> * - %DRM_XE_QUERY_CONFIG_FLAG_HAS_VRAM - Flag is set if the device
>> * has usable VRAM
>> + * - %DRM_XE_QUERY_CONFIG_FLAG_HAS_FLAT_CCS - Flag is set if the device
>> + * has flat ccs enabled
>> * - %DRM_XE_QUERY_CONFIG_MIN_ALIGNMENT - Minimal memory alignment
>> * required by this device, typically SZ_4K or SZ_64K
>> * - %DRM_XE_QUERY_CONFIG_VA_BITS - Maximum bits of a virtual address
>> @@ -405,6 +407,7 @@ struct drm_xe_query_config {
>> #define DRM_XE_QUERY_CONFIG_REV_AND_DEVICE_ID 0
>> #define DRM_XE_QUERY_CONFIG_FLAGS 1
>> #define DRM_XE_QUERY_CONFIG_FLAG_HAS_VRAM (1 << 0)
>> + #define DRM_XE_QUERY_CONFIG_FLAG_HAS_FLAT_CCS (1 << 1)
> May you point me out which kernel patch includes this flag into
> xe_query.c?
>
> --
> Zbigniew
https://patchwork.freedesktop.org/series/131609/
-- Akshata
>> #define DRM_XE_QUERY_CONFIG_MIN_ALIGNMENT 2
>> #define DRM_XE_QUERY_CONFIG_VA_BITS 3
>> #define DRM_XE_QUERY_CONFIG_MAX_EXEC_QUEUE_PRIORITY 4
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2024-03-26 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 9:54 [PATCH i-g-t v1 0/3] Add check to ensure platform supports compression Akshata Jahagirdar
2024-03-25 23:57 ` ✗ Fi.CI.BUILD: failure for " Patchwork
2024-03-26 9:54 ` [PATCH i-g-t v1 1/3] drm-uapi/xe_drm: Read flat ccs value from drm_xe_query_config Akshata Jahagirdar
2024-03-26 5:19 ` Zbigniew Kempczyński
2024-03-26 5:29 ` Jahagirdar, Akshata [this message]
2024-03-26 6:03 ` Zbigniew Kempczyński
2024-03-26 9:54 ` [PATCH i-g-t v1 2/3] lib/intel_blt: Add helper function to ensure platform supports compression Akshata Jahagirdar
2024-03-26 9:54 ` [PATCH i-g-t v1 3/3] tests/xe_ccs: Check if " Akshata Jahagirdar
2024-03-26 8:36 ` Matthew Auld
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=3b2f7338-195e-4410-b662-290550587a3b@intel.com \
--to=akshata.jahagirdar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=zbigniew.kempczynski@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