From: Jonathan Cavitt <jonathan.cavitt@intel.com>
To: igt-dev@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,
stuart.summers@intel.com, shuicheng.lin@intel.com,
nishit.sharma@intel.com, matthew.auld@intel.com,
kamil.konieczny@linux.intel.com
Subject: [PATCH v9 0/4] tests/intel/xe_vm: Add drm_xe_vm_get_property tests
Date: Wed, 1 Apr 2026 17:09:15 +0000 [thread overview]
Message-ID: <20260401170914.16908-6-jonathan.cavitt@intel.com> (raw)
Add tests that exercise the new drm_xe_vm_get_property uapi,
specifically for ioctl input validation and for determining that
pagefaults are correctly tracked and returned by the reporter.
v2:
- Remove engine class and instance (Ivan)
v3:
- Add declares for fault type, access type, and fault level (Matt Brost,
Ivan)
v4:
- Make vm creation consistent between patches (jcavitt)
- s/pageproperty/pagefaults
v5:
- Rebase
- Use correct ID for ioctl
v6:
- Rebase
v7:
- Clarify canonicity of fault address
- Use xe_vm_get_property in test
v8:
- Fix checkpatch issue - extra space in line (Sharma)
v9:
- Fix commit message (Kamil)
- Add missing invalid extensions and pad tests (Auld)
Signed-off-by: Jonathan Cavitt <joanthan.cavitt@intel.com>
Suggested-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Suggested-by: Matthew Brost <matthew.brost@intel.com>
Suggested-by: Zhang Jianxun <jianxun.zhang@intel.com>
Suggested-by: Stuart Summers <stuart.summers@intel.com>
Cc: Shuicheng Lin <shuicheng.lin@intel.com>
Cc: Ivan Briano <ivan.briano@intel.com>
Cc: Nishit Sharma <nishit.sharma@intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
Jonathan Cavitt (4):
drm-uapi/xe: Declare xe_vm_get_property_ioctl
lib/xe/xe_ioctl: Add xe_vm_get_property helper function
tests/intel/xe_vm: Add DRM_IOCTL_XE_VM_GET_PROPERTY validation tests
tests/intel/xe_vm: Test DRM_IOCTL_XE_VM_GET_PROPERTY fault reporting
include/drm-uapi/xe_drm.h | 86 +++++++++++++
lib/xe/xe_ioctl.c | 5 +
lib/xe/xe_ioctl.h | 1 +
tests/intel/xe_vm.c | 265 ++++++++++++++++++++++++++++++++++++++
4 files changed, 357 insertions(+)
--
2.43.0
next reply other threads:[~2026-04-01 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 17:09 Jonathan Cavitt [this message]
2026-04-01 17:09 ` [PATCH v9 1/4] drm-uapi/xe: Declare xe_vm_get_property_ioctl Jonathan Cavitt
2026-04-01 17:09 ` [PATCH v9 2/4] lib/xe/xe_ioctl: Add xe_vm_get_property helper function Jonathan Cavitt
2026-04-01 17:09 ` [PATCH v9 3/4] tests/intel/xe_vm: Add DRM_IOCTL_XE_VM_GET_PROPERTY validation tests Jonathan Cavitt
2026-04-01 17:09 ` [PATCH v9 4/4] tests/intel/xe_vm: Test DRM_IOCTL_XE_VM_GET_PROPERTY fault reporting Jonathan Cavitt
2026-04-01 21:15 ` ✓ Xe.CI.BAT: success for tests/intel/xe_vm: Add drm_xe_vm_get_property tests Patchwork
2026-04-01 21:47 ` ✓ i915.CI.BAT: " Patchwork
2026-04-02 4:02 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-02 16:46 ` ✗ i915.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=20260401170914.16908-6-jonathan.cavitt@intel.com \
--to=jonathan.cavitt@intel.com \
--cc=alex.zuo@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jianxun.zhang@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=nishit.sharma@intel.com \
--cc=saurabhg.gupta@intel.com \
--cc=shuicheng.lin@intel.com \
--cc=stuart.summers@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.