From: Jianxun Zhang <jianxun.zhang@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <saurabhg.gupta@intel.com>, <alex.zuo@intel.com>,
<joonas.lahtinen@linux.intel.com>, <matthew.brost@intel.com>,
<shuicheng.lin@intel.com>, <dri-devel@lists.freedesktop.org>,
<Michal.Wajdeczko@intel.com>, <michal.mrozek@intel.com>
Subject: Re: [PATCH v9 3/6] drm/xe/uapi: Define drm_xe_vm_get_property
Date: Wed, 19 Mar 2025 12:59:15 -0700 [thread overview]
Message-ID: <4f6e669c-5d80-4bf9-a7ab-eac8c0ce8000@intel.com> (raw)
In-Reply-To: <20250318171146.78571-4-jonathan.cavitt@intel.com>
On 3/18/25 10:11, 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)
>
> Signed-off-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Cc: Zhang Jianxun <jianxun.zhang@intel.com>
> ---
> include/uapi/drm/xe_drm.h | 80 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 80 insertions(+)
>
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index 616916985e3f..ef335471653e 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,83 @@ 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;
> +#define DRM_XE_FAULT_ADDRESS_TYPE_NONE_EXT 0
Just a question, VK_DEVICE_FAULT_ADDRESS_TYPE_NONE_EXT in Vulkan spec
specifies the address of the fault does not describe a page fault, or an
instruction address. Does this NONE type in KMD mean the same thing?
> +#define DRM_XE_FAULT_ADDRESS_TYPE_READ_INVALID_EXT 1
> +#define DRM_XE_FAULT_ADDRESS_TYPE_WRITE_INVALID_EXT 2
> + /** @address_type: Type of address access that resulted in fault */
> + __u32 address_type;
> + /** @address_precision: Precision of faulted address */
> + __u32 address_precision;
> + /** @fault_level: fault level of the fault */
> + __u8 fault_level;
> + /** @engine_class: class of engine fault was reported on */
> + __u8 engine_class;
> + /** @engine_instance: instance of engine fault was reported on */
> + __u8 engine_instance;
> + /** @pad: MBZ */
> + __u8 pad[5];
> + /** @reserved: MBZ */
> + __u64 reserved[3];
> +};
> +
> +/**
> + * 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
> *
next prev parent reply other threads:[~2025-03-19 19:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 17:11 [PATCH v9 0/6] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-03-18 17:11 ` [PATCH v9 1/6] drm/xe/xe_gt_pagefault: Disallow writes to read-only VMAs Jonathan Cavitt
2025-03-18 17:11 ` [PATCH v9 2/6] drm/xe/xe_gt_pagefault: Move pagefault struct to header Jonathan Cavitt
2025-03-18 18:37 ` Michal Wajdeczko
2025-03-18 20:12 ` Cavitt, Jonathan
2025-03-18 22:01 ` Michal Wajdeczko
2025-03-19 15:26 ` Cavitt, Jonathan
2025-03-18 17:11 ` [PATCH v9 3/6] drm/xe/uapi: Define drm_xe_vm_get_property Jonathan Cavitt
2025-03-19 19:59 ` Jianxun Zhang [this message]
2025-03-19 20:13 ` Cavitt, Jonathan
2025-03-19 21:02 ` Zhang, Jianxun
2025-03-19 21:13 ` Cavitt, Jonathan
2025-03-19 22:33 ` Jianxun Zhang
2025-03-18 17:11 ` [PATCH v9 4/6] drm/xe/xe_gt_pagefault: Add address_type field to pagefaults Jonathan Cavitt
2025-03-18 17:11 ` [PATCH v9 5/6] drm/xe/xe_vm: Add per VM fault info Jonathan Cavitt
2025-03-18 17:11 ` [PATCH v9 6/6] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-03-18 17:16 ` ✓ CI.Patch_applied: success for drm/xe/xe_vm: Implement xe_vm_get_property_ioctl (rev10) Patchwork
2025-03-18 17:16 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-18 17:17 ` ✓ CI.KUnit: success " Patchwork
2025-03-18 17:34 ` ✓ CI.Build: " Patchwork
2025-03-18 17:36 ` ✓ CI.Hooks: " Patchwork
2025-03-18 17:38 ` ✓ CI.checksparse: " Patchwork
2025-03-18 17:57 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-18 18:55 ` ✗ Xe.CI.Full: failure " 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=4f6e669c-5d80-4bf9-a7ab-eac8c0ce8000@intel.com \
--to=jianxun.zhang@intel.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=alex.zuo@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=michal.mrozek@intel.com \
--cc=saurabhg.gupta@intel.com \
--cc=shuicheng.lin@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