| Message ID | 20250401222657.78545-4-jonathan.cavitt@intel.com (mailing list archive) |
|---|---|
| State | New |
| Headers | show |
| Series | drm/xe/xe_vm: Implement xe_vm_get_property_ioctl | expand |
On Tue, Apr 01, 2025 at 10:26:54PM +0000, Jonathan Cavitt wrote: > +/** struct xe_vm_fault - Describes faults for %DRM_XE_VM_GET_PROPERTY_FAULTS */ > +struct xe_vm_fault { > + /** @address: Address of the fault */ > + __u64 address; > + /** @address_precision: Precision of faulted address */ > + __u32 address_precision; > + /** @access_type: Type of address access that resulted in fault */ > + __u8 access_type; > + /** @fault_type: Type of fault reported */ > + __u8 fault_type; > + /** @fault_level: fault level of the fault */ > + __u8 fault_level; > + /** @pad: MBZ */ > + __u8 pad; > + /** @reserved: MBZ */ > + __u64 reserved[4]; > +}; Are the possible values here documented somewhere or should be just follow bspec for them?
On 4/1/25 15:26, Jonathan Cavitt wrote: > Add initial declarations for the drm_xe_vm_get_property ioctl. > > v2: > - Expand kernel docs for drm_xe_vm_get_property (Jianxun) > > v3: > - Remove address type external definitions (Jianxun) > - Add fault type to xe_drm_fault struct (Jianxun) > > v4: > - Remove engine class and instance (Ivan) > > Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com> > Cc: Zhang Jianxun <jianxun.zhang@intel.com> > Cc: Ivan Briano <ivan.briano@intel.com> > --- > include/uapi/drm/xe_drm.h | 75 +++++++++++++++++++++++++++++++++++++++ > 1 file changed, 75 insertions(+) > > diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h > index 616916985e3f..45f7560879cb 100644 > --- a/include/uapi/drm/xe_drm.h > +++ b/include/uapi/drm/xe_drm.h > @@ -81,6 +81,7 @@ extern "C" { > * - &DRM_IOCTL_XE_EXEC > * - &DRM_IOCTL_XE_WAIT_USER_FENCE > * - &DRM_IOCTL_XE_OBSERVATION > + * - &DRM_IOCTL_XE_VM_GET_PROPERTY > */ > > /* > @@ -102,6 +103,7 @@ extern "C" { > #define DRM_XE_EXEC 0x09 > #define DRM_XE_WAIT_USER_FENCE 0x0a > #define DRM_XE_OBSERVATION 0x0b > +#define DRM_XE_VM_GET_PROPERTY 0x0c > > /* Must be kept compact -- no holes */ > > @@ -117,6 +119,7 @@ extern "C" { > #define DRM_IOCTL_XE_EXEC DRM_IOW(DRM_COMMAND_BASE + DRM_XE_EXEC, struct drm_xe_exec) > #define DRM_IOCTL_XE_WAIT_USER_FENCE DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_WAIT_USER_FENCE, struct drm_xe_wait_user_fence) > #define DRM_IOCTL_XE_OBSERVATION DRM_IOW(DRM_COMMAND_BASE + DRM_XE_OBSERVATION, struct drm_xe_observation_param) > +#define DRM_IOCTL_XE_VM_GET_PROPERTY DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_VM_GET_PROPERTY, struct drm_xe_vm_get_property) > > /** > * DOC: Xe IOCTL Extensions > @@ -1189,6 +1192,78 @@ struct drm_xe_vm_bind { > __u64 reserved[2]; > }; > > +/** struct xe_vm_fault - Describes faults for %DRM_XE_VM_GET_PROPERTY_FAULTS */ > +struct xe_vm_fault { > + /** @address: Address of the fault */ > + __u64 address; > + /** @address_precision: Precision of faulted address */ > + __u32 address_precision; > + /** @access_type: Type of address access that resulted in fault */ > + __u8 access_type; > + /** @fault_type: Type of fault reported */ > + __u8 fault_type; > + /** @fault_level: fault level of the fault */ > + __u8 fault_level; > + /** @pad: MBZ */ > + __u8 pad; > + /** @reserved: MBZ */ > + __u64 reserved[4]; Why are engine class and instance gone? I think we got agreement on not reporting class 0x4, but the rest should be kept. If KMD can have these in dmesg, why can't we report these in VK report? > +}; > + > +/** > + * struct drm_xe_vm_get_property - Input of &DRM_IOCTL_XE_VM_GET_PROPERTY > + * > + * The user provides a VM and a property to query among DRM_XE_VM_GET_PROPERTY_*, > + * and sets the values in the vm_id and property members, respectively. This > + * determines both the VM to get the property of, as well as the property to > + * report. > + * > + * If size is set to 0, the driver fills it with the required size for the > + * requested property. The user is expected here to allocate memory for the > + * property structure and to provide a pointer to the allocated memory using the > + * data member. For some properties, this may be zero, in which case, the > + * value of the property will be saved to the value member and size will remain > + * zero on return. > + * > + * If size is not zero, then the IOCTL will attempt to copy the requested > + * property into the data member. > + * > + * The IOCTL will return -ENOENT if the VM could not be identified from the > + * provided VM ID, or -EINVAL if the IOCTL fails for any other reason, such as > + * providing an invalid size for the given property or if the property data > + * could not be copied to the memory allocated to the data member. > + * > + * The property member can be: > + * - %DRM_XE_VM_GET_PROPERTY_FAULTS > + */ > +struct drm_xe_vm_get_property { > + /** @extensions: Pointer to the first extension struct, if any */ > + __u64 extensions; > + > + /** @vm_id: The ID of the VM to query the properties of */ > + __u32 vm_id; > + > +#define DRM_XE_VM_GET_PROPERTY_FAULTS 0 > + /** @property: property to get */ > + __u32 property; > + > + /** @size: Size to allocate for @data */ > + __u32 size; > + > + /** @pad: MBZ */ > + __u32 pad; > + > + union { > + /** @data: Pointer to user-defined array of flexible size and type */ > + __u64 data; > + /** @value: Return value for scalar queries */ > + __u64 value; > + }; > + > + /** @reserved: MBZ */ > + __u64 reserved[3]; > +}; > + > /** > * struct drm_xe_exec_queue_create - Input of &DRM_IOCTL_XE_EXEC_QUEUE_CREATE > *
On 4/2/25 18:19, Jianxun Zhang wrote: > > > On 4/1/25 15:26, Jonathan Cavitt wrote: >> Add initial declarations for the drm_xe_vm_get_property ioctl. >> >> v2: >> - Expand kernel docs for drm_xe_vm_get_property (Jianxun) >> >> v3: >> - Remove address type external definitions (Jianxun) >> - Add fault type to xe_drm_fault struct (Jianxun) >> >> v4: >> - Remove engine class and instance (Ivan) >> >> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com> >> Cc: Zhang Jianxun <jianxun.zhang@intel.com> >> Cc: Ivan Briano <ivan.briano@intel.com> >> --- >> include/uapi/drm/xe_drm.h | 75 +++++++++++++++++++++++++++++++++++++++ >> 1 file changed, 75 insertions(+) >> >> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h >> index 616916985e3f..45f7560879cb 100644 >> --- a/include/uapi/drm/xe_drm.h >> +++ b/include/uapi/drm/xe_drm.h >> @@ -81,6 +81,7 @@ extern "C" { >> * - &DRM_IOCTL_XE_EXEC >> * - &DRM_IOCTL_XE_WAIT_USER_FENCE >> * - &DRM_IOCTL_XE_OBSERVATION >> + * - &DRM_IOCTL_XE_VM_GET_PROPERTY >> */ >> /* >> @@ -102,6 +103,7 @@ extern "C" { >> #define DRM_XE_EXEC 0x09 >> #define DRM_XE_WAIT_USER_FENCE 0x0a >> #define DRM_XE_OBSERVATION 0x0b >> +#define DRM_XE_VM_GET_PROPERTY 0x0c >> /* Must be kept compact -- no holes */ >> @@ -117,6 +119,7 @@ extern "C" { >> #define DRM_IOCTL_XE_EXEC DRM_IOW(DRM_COMMAND_BASE + >> DRM_XE_EXEC, struct drm_xe_exec) >> #define DRM_IOCTL_XE_WAIT_USER_FENCE >> DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_WAIT_USER_FENCE, struct >> drm_xe_wait_user_fence) >> #define DRM_IOCTL_XE_OBSERVATION DRM_IOW(DRM_COMMAND_BASE + >> DRM_XE_OBSERVATION, struct drm_xe_observation_param) >> +#define DRM_IOCTL_XE_VM_GET_PROPERTY DRM_IOWR(DRM_COMMAND_BASE + >> DRM_XE_VM_GET_PROPERTY, struct drm_xe_vm_get_property) >> /** >> * DOC: Xe IOCTL Extensions >> @@ -1189,6 +1192,78 @@ struct drm_xe_vm_bind { >> __u64 reserved[2]; >> }; >> +/** struct xe_vm_fault - Describes faults for >> %DRM_XE_VM_GET_PROPERTY_FAULTS */ >> +struct xe_vm_fault { >> + /** @address: Address of the fault */ >> + __u64 address; >> + /** @address_precision: Precision of faulted address */ >> + __u32 address_precision; >> + /** @access_type: Type of address access that resulted in fault */ >> + __u8 access_type; >> + /** @fault_type: Type of fault reported */ >> + __u8 fault_type; >> + /** @fault_level: fault level of the fault */ >> + __u8 fault_level; >> + /** @pad: MBZ */ >> + __u8 pad; >> + /** @reserved: MBZ */ >> + __u64 reserved[4]; > Why are engine class and instance gone? I think we got agreement on not > reporting class 0x4, but the rest should be kept. If KMD can have these > in dmesg, why can't we report these in VK report? Never mind. I just caught up with the offline traffic. I have no opinion on this. Thanks. >> +}; >> + >> +/** >> + * struct drm_xe_vm_get_property - Input of >> &DRM_IOCTL_XE_VM_GET_PROPERTY >> + * >> + * The user provides a VM and a property to query among >> DRM_XE_VM_GET_PROPERTY_*, >> + * and sets the values in the vm_id and property members, >> respectively. This >> + * determines both the VM to get the property of, as well as the >> property to >> + * report. >> + * >> + * If size is set to 0, the driver fills it with the required size >> for the >> + * requested property. The user is expected here to allocate memory >> for the >> + * property structure and to provide a pointer to the allocated >> memory using the >> + * data member. For some properties, this may be zero, in which >> case, the >> + * value of the property will be saved to the value member and size >> will remain >> + * zero on return. >> + * >> + * If size is not zero, then the IOCTL will attempt to copy the >> requested >> + * property into the data member. >> + * >> + * The IOCTL will return -ENOENT if the VM could not be identified >> from the >> + * provided VM ID, or -EINVAL if the IOCTL fails for any other >> reason, such as >> + * providing an invalid size for the given property or if the >> property data >> + * could not be copied to the memory allocated to the data member. >> + * >> + * The property member can be: >> + * - %DRM_XE_VM_GET_PROPERTY_FAULTS >> + */ >> +struct drm_xe_vm_get_property { >> + /** @extensions: Pointer to the first extension struct, if any */ >> + __u64 extensions; >> + >> + /** @vm_id: The ID of the VM to query the properties of */ >> + __u32 vm_id; >> + >> +#define DRM_XE_VM_GET_PROPERTY_FAULTS 0 >> + /** @property: property to get */ >> + __u32 property; >> + >> + /** @size: Size to allocate for @data */ >> + __u32 size; >> + >> + /** @pad: MBZ */ >> + __u32 pad; >> + >> + union { >> + /** @data: Pointer to user-defined array of flexible size and >> type */ >> + __u64 data; >> + /** @value: Return value for scalar queries */ >> + __u64 value; >> + }; >> + >> + /** @reserved: MBZ */ >> + __u64 reserved[3]; >> +}; >> + >> /** >> * struct drm_xe_exec_queue_create - Input of >> &DRM_IOCTL_XE_EXEC_QUEUE_CREATE >> * >
-----Original Message----- From: Briano, Ivan <ivan.briano@intel.com> Sent: Wednesday, April 2, 2025 4:22 PM To: Cavitt, Jonathan <jonathan.cavitt@intel.com> Cc: intel-xe@lists.freedesktop.org; Gupta, saurabhg <saurabhg.gupta@intel.com>; Zuo, Alex <alex.zuo@intel.com>; joonas.lahtinen@linux.intel.com; Brost, Matthew <matthew.brost@intel.com>; Zhang, Jianxun <jianxun.zhang@intel.com>; Lin, Shuicheng <shuicheng.lin@intel.com>; dri-devel@lists.freedesktop.org; Wajdeczko, Michal <Michal.Wajdeczko@intel.com>; Mrozek, Michal <michal.mrozek@intel.com>; Jadav, Raag <raag.jadav@intel.com>; Harrison, John C <john.c.harrison@intel.com> Subject: Re: [PATCH v16 3/5] drm/xe/uapi: Define drm_xe_vm_get_property > > On Tue, Apr 01, 2025 at 10:26:54PM +0000, Jonathan Cavitt wrote: > > +/** struct xe_vm_fault - Describes faults for %DRM_XE_VM_GET_PROPERTY_FAULTS */ > > +struct xe_vm_fault { > > + /** @address: Address of the fault */ > > + __u64 address; > > + /** @address_precision: Precision of faulted address */ > > + __u32 address_precision; > > + /** @access_type: Type of address access that resulted in fault */ > > + __u8 access_type; > > + /** @fault_type: Type of fault reported */ > > + __u8 fault_type; > > + /** @fault_level: fault level of the fault */ > > + __u8 fault_level; > > + /** @pad: MBZ */ > > + __u8 pad; > > + /** @reserved: MBZ */ > > + __u64 reserved[4]; > > +}; > > Are the possible values here documented somewhere or should be just > follow bspec for them? I think bspec is currently being used for access_type, fault_type, and fault_level. However, I can add the possible values to the kernel docs if you feel that is pertinent. The address and address precision don't necessarily follow any currently documented bspec specifications, but they should be self-explanatory enough that it's not needed. -Jonathan Cavitt >
On Thu, Apr 03, 2025 at 09:24:47AM -0700, Cavitt, Jonathan wrote: > -----Original Message----- > From: Briano, Ivan <ivan.briano@intel.com> > Sent: Wednesday, April 2, 2025 4:22 PM > To: Cavitt, Jonathan <jonathan.cavitt@intel.com> > Cc: intel-xe@lists.freedesktop.org; Gupta, saurabhg <saurabhg.gupta@intel.com>; Zuo, Alex <alex.zuo@intel.com>; joonas.lahtinen@linux.intel.com; Brost, Matthew <matthew.brost@intel.com>; Zhang, Jianxun <jianxun.zhang@intel.com>; Lin, Shuicheng <shuicheng.lin@intel.com>; dri-devel@lists.freedesktop.org; Wajdeczko, Michal <Michal.Wajdeczko@intel.com>; Mrozek, Michal <michal.mrozek@intel.com>; Jadav, Raag <raag.jadav@intel.com>; Harrison, John C <john.c.harrison@intel.com> > Subject: Re: [PATCH v16 3/5] drm/xe/uapi: Define drm_xe_vm_get_property > > > > On Tue, Apr 01, 2025 at 10:26:54PM +0000, Jonathan Cavitt wrote: > > > +/** struct xe_vm_fault - Describes faults for %DRM_XE_VM_GET_PROPERTY_FAULTS */ > > > +struct xe_vm_fault { > > > + /** @address: Address of the fault */ > > > + __u64 address; > > > + /** @address_precision: Precision of faulted address */ > > > + __u32 address_precision; > > > + /** @access_type: Type of address access that resulted in fault */ > > > + __u8 access_type; > > > + /** @fault_type: Type of fault reported */ > > > + __u8 fault_type; > > > + /** @fault_level: fault level of the fault */ > > > + __u8 fault_level; > > > + /** @pad: MBZ */ > > > + __u8 pad; > > > + /** @reserved: MBZ */ > > > + __u64 reserved[4]; > > > +}; > > > > Are the possible values here documented somewhere or should be just > > follow bspec for them? > > I think bspec is currently being used for access_type, fault_type, and fault_level. > However, I can add the possible values to the kernel docs if you feel that is > pertinent. > It's more of a question of API stability. If the HW changes how it reports this, do we get different values in different platforms, or do we want to fix them here?
-----Original Message----- From: Briano, Ivan <ivan.briano@intel.com> Sent: Thursday, April 3, 2025 9:46 AM To: Cavitt, Jonathan <jonathan.cavitt@intel.com> Cc: intel-xe@lists.freedesktop.org; Gupta, saurabhg <saurabhg.gupta@intel.com>; Zuo, Alex <alex.zuo@intel.com>; joonas.lahtinen@linux.intel.com; Brost, Matthew <matthew.brost@intel.com>; Zhang, Jianxun <jianxun.zhang@intel.com>; Lin, Shuicheng <shuicheng.lin@intel.com>; dri-devel@lists.freedesktop.org; Wajdeczko, Michal <Michal.Wajdeczko@intel.com>; Mrozek, Michal <michal.mrozek@intel.com>; Jadav, Raag <raag.jadav@intel.com>; Harrison, John C <john.c.harrison@intel.com> Subject: Re: [PATCH v16 3/5] drm/xe/uapi: Define drm_xe_vm_get_property > > On Thu, Apr 03, 2025 at 09:24:47AM -0700, Cavitt, Jonathan wrote: > > -----Original Message----- > > From: Briano, Ivan <ivan.briano@intel.com> > > Sent: Wednesday, April 2, 2025 4:22 PM > > To: Cavitt, Jonathan <jonathan.cavitt@intel.com> > > Cc: intel-xe@lists.freedesktop.org; Gupta, saurabhg <saurabhg.gupta@intel.com>; Zuo, Alex <alex.zuo@intel.com>; joonas.lahtinen@linux.intel.com; Brost, Matthew <matthew.brost@intel.com>; Zhang, Jianxun <jianxun.zhang@intel.com>; Lin, Shuicheng <shuicheng.lin@intel.com>; dri-devel@lists.freedesktop.org; Wajdeczko, Michal <Michal.Wajdeczko@intel.com>; Mrozek, Michal <michal.mrozek@intel.com>; Jadav, Raag <raag.jadav@intel.com>; Harrison, John C <john.c.harrison@intel.com> > > Subject: Re: [PATCH v16 3/5] drm/xe/uapi: Define drm_xe_vm_get_property > > > > > > On Tue, Apr 01, 2025 at 10:26:54PM +0000, Jonathan Cavitt wrote: > > > > +/** struct xe_vm_fault - Describes faults for %DRM_XE_VM_GET_PROPERTY_FAULTS */ > > > > +struct xe_vm_fault { > > > > + /** @address: Address of the fault */ > > > > + __u64 address; > > > > + /** @address_precision: Precision of faulted address */ > > > > + __u32 address_precision; > > > > + /** @access_type: Type of address access that resulted in fault */ > > > > + __u8 access_type; > > > > + /** @fault_type: Type of fault reported */ > > > > + __u8 fault_type; > > > > + /** @fault_level: fault level of the fault */ > > > > + __u8 fault_level; > > > > + /** @pad: MBZ */ > > > > + __u8 pad; > > > > + /** @reserved: MBZ */ > > > > + __u64 reserved[4]; > > > > +}; > > > > > > Are the possible values here documented somewhere or should be just > > > follow bspec for them? > > > > I think bspec is currently being used for access_type, fault_type, and fault_level. > > However, I can add the possible values to the kernel docs if you feel that is > > pertinent. > > > > It's more of a question of API stability. If the HW changes how it > reports this, do we get different values in different platforms, or do > we want to fix them here? Revision note applied: Added macros for access type, fault type, and fault level in latest revision. FYI @Brost, Matthew -Jonathan Cavitt >
diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h index 616916985e3f..45f7560879cb 100644 --- a/include/uapi/drm/xe_drm.h +++ b/include/uapi/drm/xe_drm.h @@ -81,6 +81,7 @@ extern "C" { * - &DRM_IOCTL_XE_EXEC * - &DRM_IOCTL_XE_WAIT_USER_FENCE * - &DRM_IOCTL_XE_OBSERVATION + * - &DRM_IOCTL_XE_VM_GET_PROPERTY */ /* @@ -102,6 +103,7 @@ extern "C" { #define DRM_XE_EXEC 0x09 #define DRM_XE_WAIT_USER_FENCE 0x0a #define DRM_XE_OBSERVATION 0x0b +#define DRM_XE_VM_GET_PROPERTY 0x0c /* Must be kept compact -- no holes */ @@ -117,6 +119,7 @@ extern "C" { #define DRM_IOCTL_XE_EXEC DRM_IOW(DRM_COMMAND_BASE + DRM_XE_EXEC, struct drm_xe_exec) #define DRM_IOCTL_XE_WAIT_USER_FENCE DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_WAIT_USER_FENCE, struct drm_xe_wait_user_fence) #define DRM_IOCTL_XE_OBSERVATION DRM_IOW(DRM_COMMAND_BASE + DRM_XE_OBSERVATION, struct drm_xe_observation_param) +#define DRM_IOCTL_XE_VM_GET_PROPERTY DRM_IOWR(DRM_COMMAND_BASE + DRM_XE_VM_GET_PROPERTY, struct drm_xe_vm_get_property) /** * DOC: Xe IOCTL Extensions @@ -1189,6 +1192,78 @@ struct drm_xe_vm_bind { __u64 reserved[2]; }; +/** struct xe_vm_fault - Describes faults for %DRM_XE_VM_GET_PROPERTY_FAULTS */ +struct xe_vm_fault { + /** @address: Address of the fault */ + __u64 address; + /** @address_precision: Precision of faulted address */ + __u32 address_precision; + /** @access_type: Type of address access that resulted in fault */ + __u8 access_type; + /** @fault_type: Type of fault reported */ + __u8 fault_type; + /** @fault_level: fault level of the fault */ + __u8 fault_level; + /** @pad: MBZ */ + __u8 pad; + /** @reserved: MBZ */ + __u64 reserved[4]; +}; + +/** + * struct drm_xe_vm_get_property - Input of &DRM_IOCTL_XE_VM_GET_PROPERTY + * + * The user provides a VM and a property to query among DRM_XE_VM_GET_PROPERTY_*, + * and sets the values in the vm_id and property members, respectively. This + * determines both the VM to get the property of, as well as the property to + * report. + * + * If size is set to 0, the driver fills it with the required size for the + * requested property. The user is expected here to allocate memory for the + * property structure and to provide a pointer to the allocated memory using the + * data member. For some properties, this may be zero, in which case, the + * value of the property will be saved to the value member and size will remain + * zero on return. + * + * If size is not zero, then the IOCTL will attempt to copy the requested + * property into the data member. + * + * The IOCTL will return -ENOENT if the VM could not be identified from the + * provided VM ID, or -EINVAL if the IOCTL fails for any other reason, such as + * providing an invalid size for the given property or if the property data + * could not be copied to the memory allocated to the data member. + * + * The property member can be: + * - %DRM_XE_VM_GET_PROPERTY_FAULTS + */ +struct drm_xe_vm_get_property { + /** @extensions: Pointer to the first extension struct, if any */ + __u64 extensions; + + /** @vm_id: The ID of the VM to query the properties of */ + __u32 vm_id; + +#define DRM_XE_VM_GET_PROPERTY_FAULTS 0 + /** @property: property to get */ + __u32 property; + + /** @size: Size to allocate for @data */ + __u32 size; + + /** @pad: MBZ */ + __u32 pad; + + union { + /** @data: Pointer to user-defined array of flexible size and type */ + __u64 data; + /** @value: Return value for scalar queries */ + __u64 value; + }; + + /** @reserved: MBZ */ + __u64 reserved[3]; +}; + /** * struct drm_xe_exec_queue_create - Input of &DRM_IOCTL_XE_EXEC_QUEUE_CREATE *
Add initial declarations for the drm_xe_vm_get_property ioctl. v2: - Expand kernel docs for drm_xe_vm_get_property (Jianxun) v3: - Remove address type external definitions (Jianxun) - Add fault type to xe_drm_fault struct (Jianxun) v4: - Remove engine class and instance (Ivan) Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com> Cc: Zhang Jianxun <jianxun.zhang@intel.com> Cc: Ivan Briano <ivan.briano@intel.com> --- include/uapi/drm/xe_drm.h | 75 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 75 insertions(+)