From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: saurabhg.gupta@intel.com, alex.zuo@intel.com,
jonathan.cavitt@intel.com, joonas.lahtinen@linux.intel.com,
matthew.brost@intel.com, jianxun.zhang@intel.com,
dri-devel@lists.freedesktop.org
Subject: [PATCH v2 6/8] drm/xe/uapi: Define drm_xe_vm_get_property
Date: Thu, 27 Feb 2025 19:14:55 +0000 [thread overview]
Message-ID: <20250227191457.84035-7-jonathan.cavitt@intel.com> (raw)
In-Reply-To: <20250227191457.84035-1-jonathan.cavitt@intel.com>
Add initial declarations for the drm_xe_vm_get_property ioctl.
Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
---
include/uapi/drm/xe_drm.h | 67 +++++++++++++++++++++++++++++++++++++++
1 file changed, 67 insertions(+)
diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
index 76a462fae05f..78a5285bc5f8 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
@@ -1166,6 +1169,70 @@ struct drm_xe_vm_bind {
__u64 reserved[2];
};
+struct drm_xe_ban {
+ /** @exec_queue_id: ID of banned exec queue */
+ __u32 exec_queue_id;
+ /** @faulted: Whether or not the ban has an associated pagefault. 0 is no, 1 is yes */
+ __u32 faulted;
+ /** @address: Address of the fault, if relevant */
+ __u64 address;
+#define DRM_XE_FAULT_ADDRESS_TYPE_NONE_EXT 0
+#define DRM_XE_FAULT_ADDRESS_TYPE_READ_INVALID_EXT 1
+#define DRM_XE_FAULT_ADDRESS_TYPE_WRITE_INVALID_EXT 2
+ /** @address_type: , if relevant */
+ __u32 address_type;
+ /**
+ * @address_precision: Precision of faulted address, if relevant.
+ * Currently only SZ_4K.
+ */
+ __u32 address_precision;
+ /** @reserved: MBZ */
+ __u64 reserved[3];
+};
+
+/**
+ * struct drm_xe_vm_get_property - Input of &DRM_IOCTL_XE_VM_GET_PROPERTY
+ *
+ * The user provides a VM ID and a property to query to this ioctl,
+ * and the ioctl returns the size of the return value. Calling the
+ * ioctl again with memory reserved for the data will save the
+ * requested property data to the data pointer.
+ *
+ * The valid properties are:
+ * - %DRM_XE_VM_GET_PROPERTY_FAULTS : List of all pagefaults that resulted in exec queue bans
+ * - %DRM_XE_VM_GET_PROPERTY_BANS : List of all exec queue bans
+ * - %DRM_XE_VM_GET_PROPERTY_NUM_RESETS : Number of engine resets seen by VM.
+ */
+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
+#define DRM_XE_VM_GET_PROPERTY_BANS 1
+#define DRM_XE_VM_GET_PROPERTY_NUM_RESETS 2
+ /** @property: The property to get */
+ __u32 property;
+
+ /** @size: Size of returned property @data */
+ __u32 size;
+
+ /** @pad: MBZ */
+ __u32 pad;
+
+ union {
+ /** @data: Return for scalar data values */
+ __u64 data;
+ /** @ptr: Pointer to user structs when required */
+ __u64 ptr;
+ };
+
+ /** @reserved: MBZ */
+ __u64 reserved[2];
+};
+
/**
* struct drm_xe_exec_queue_create - Input of &DRM_IOCTL_XE_EXEC_QUEUE_CREATE
*
--
2.43.0
next prev parent reply other threads:[~2025-02-27 19:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 19:14 [PATCH v2 0/8] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 1/8] drm/xe/xe_gt_pagefault: Disallow writes to read-only VMAs Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 2/8] drm/xe/xe_exec_queue: Add ID param to exec queue struct Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 3/8] drm/xe/xe_gt_pagefault: Migrate pagefault struct to header Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 4/8] drm/xe/xe_vm: Add per VM pagefault info Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 5/8] drm/xe/xe_vm: Add per VM reset stats Jonathan Cavitt
2025-02-27 19:14 ` Jonathan Cavitt [this message]
2025-02-27 19:14 ` [PATCH v2 7/8] drm/xe/xe_gt_pagefault: Add address_type field to pagefaults Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 8/8] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-02-28 3:44 ` kernel test robot
2025-02-27 21:01 ` ✓ CI.Patch_applied: success for drm/xe/xe_vm: Implement xe_vm_get_property_ioctl (rev2) Patchwork
2025-02-27 21:01 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-27 21:02 ` ✓ CI.KUnit: success " Patchwork
2025-02-27 21:19 ` ✓ CI.Build: " Patchwork
2025-02-27 21:21 ` ✓ CI.Hooks: " Patchwork
2025-02-27 21:23 ` ✓ CI.checksparse: " Patchwork
2025-02-27 21:43 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-02-28 2:08 ` ✗ Xe.CI.Full: " 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=20250227191457.84035-7-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jianxun.zhang@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=saurabhg.gupta@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