intel: Sync xe_drm.h

Based on commit f6e26dff8fa3 ("drm/xe: Add max engine priority to xe query")

Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22112>

diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
index 593b01b..b0b80aa 100644 (file)
--- a/include/drm-uapi/xe_drm.h
+++ b/include/drm-uapi/xe_drm.h
@@ -37,7 +37,7 @@ extern "C" {
  */
 
 /**
- * struct i915_user_extension - Base class for defining a chain of extensions
+ * struct xe_user_extension - Base class for defining a chain of extensions
  *
  * Many interfaces need to grow over time. In most cases we can simply
  * extend the struct and have userspace pass in more data. Another option,
@@ -55,20 +55,20 @@ extern "C" {
  *
  * .. code-block:: C
  *
- *     struct i915_user_extension ext3 {
+ *     struct xe_user_extension ext3 {
  *             .next_extension = 0, // end
  *             .name = ...,
  *     };
- *     struct i915_user_extension ext2 {
+ *     struct xe_user_extension ext2 {
  *             .next_extension = (uintptr_t)&ext3,
  *             .name = ...,
  *     };
- *     struct i915_user_extension ext1 {
+ *     struct xe_user_extension ext1 {
  *             .next_extension = (uintptr_t)&ext2,
  *             .name = ...,
  *     };
  *
- * Typically the struct i915_user_extension would be embedded in some uAPI
+ * Typically the struct xe_user_extension would be embedded in some uAPI
  * struct, and in this case we would feed it the head of the chain(i.e ext1),
  * which would then apply all of the above extensions.
  *
@@ -77,7 +77,7 @@ struct xe_user_extension {
        /**
         * @next_extension:
         *
-        * Pointer to the next struct i915_user_extension, or zero if the end.
+        * Pointer to the next struct xe_user_extension, or zero if the end.
         */
        __u64 next_extension;
        /**
@@ -87,7 +87,7 @@ struct xe_user_extension {
         *
         * Also note that the name space for this is not global for the whole
         * driver, but rather its scope/meaning is limited to the specific piece
-        * of uAPI which has embedded the struct i915_user_extension.
+        * of uAPI which has embedded the struct xe_user_extension.
         */
        __u32 name;
        /**
@@ -99,7 +99,7 @@ struct xe_user_extension {
 };
 
 /*
- * i915 specific ioctls.
+ * xe specific ioctls.
  *
  * The device specific ioctl range is [DRM_COMMAND_BASE, DRM_COMMAND_END) ie
  * [0x40, 0xa0) (a0 is excluded). The numbers below are defined as offset
@@ -184,7 +184,8 @@ struct drm_xe_query_config {
 #define XE_QUERY_CONFIG_VA_BITS                        3
 #define XE_QUERY_CONFIG_GT_COUNT               4
 #define XE_QUERY_CONFIG_MEM_REGION_COUNT       5
-#define XE_QUERY_CONFIG_NUM_PARAM              XE_QUERY_CONFIG_MEM_REGION_COUNT + 1
+#define XE_QUERY_CONFIG_MAX_ENGINE_PRIORITY    6
+#define XE_QUERY_CONFIG_NUM_PARAM              XE_QUERY_CONFIG_MAX_ENGINE_PRIORITY + 1
        __u64 info[];
 };