From: Nirmoy Das <nirmoy.das@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Nirmoy Das <nirmoy.das@intel.com>
Subject: [PATCH i-g-t v3 2/4] drm-uapi/xe: Add query flag for dev atomics on SMEM
Date: Mon, 15 Apr 2024 16:35:26 +0200 [thread overview]
Message-ID: <20240415143528.4107-3-nirmoy.das@intel.com> (raw)
In-Reply-To: <20240415143528.4107-1-nirmoy.das@intel.com>
Align with commit ("drm/xe/uapi: Add a query flag for
has_device_atomics_on_smem")
Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
---
include/drm-uapi/xe_drm.h | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
index 9171cc0f1..f898ea6d2 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_DEV_ATOMIC_ON_SMEM - Flag is set if the device
+ * supports device atomics on system memory
* - %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
@@ -404,7 +406,8 @@ 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_VRAM (1 << 0)
+ #define DRM_XE_QUERY_CONFIG_FLAG_HAS_DEV_ATOMIC_ON_SMEM (1 << 1)
#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.42.0
next prev parent reply other threads:[~2024-04-15 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 14:35 [PATCH i-g-t v3 0/4] Update for atomics related uAPI changes Nirmoy Das
2024-04-15 14:35 ` [PATCH i-g-t v3 1/4] drm-uapi/xe: Add device atomics vm bind flags Nirmoy Das
2024-04-15 14:35 ` Nirmoy Das [this message]
2024-04-15 14:35 ` [PATCH i-g-t v3 3/4] tests/intel/xe_exec_atomic: Use new vm bind flag Nirmoy Das
2024-04-16 9:39 ` Kumar, Janga Rahul
2024-04-15 14:35 ` [PATCH i-g-t v3 4/4] test/intel/xe_query: Print DRM_XE_QUERY_CONFIG_FLAG_HAS_DEV_ATOMIC_ON_SMEM Nirmoy Das
2024-04-16 9:35 ` Kumar, Janga Rahul
2024-04-16 7:15 ` ✓ Fi.CI.BAT: success for Update for atomics related uAPI changes Patchwork
2024-04-16 7:26 ` ✗ CI.xeBAT: failure " Patchwork
2024-04-16 18:12 ` ✓ Fi.CI.IGT: success " Patchwork
2024-04-17 3:27 ` ✗ CI.xeFULL: failure " Patchwork
2024-04-17 10:09 ` Kamil Konieczny
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=20240415143528.4107-3-nirmoy.das@intel.com \
--to=nirmoy.das@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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