From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org, thomas.hellstrom@intel.com
Cc: nishit.sharma@intel.com, Sobin Thomas <sobin.thomas@intel.com>
Subject: [PATCH v2 i-g-t 1/2] drm-uapi/xe: Add support for No Overcommit flag
Date: Mon, 2 Mar 2026 14:00:09 +0000 [thread overview]
Message-ID: <20260302140010.1009564-2-sobin.thomas@intel.com> (raw)
In-Reply-To: <20260302140010.1009564-1-sobin.thomas@intel.com>
Align with kernel commit 369cc8804985 ("drm/xe/uapi: Introduce a flag to
disallow VM overcommit in fault mode"). This adds support for the No
Overcommit flag in IGT to match the kernel UAPI behavior.
Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
---
include/drm-uapi/xe_drm.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
index 077e66a68..12a9da045 100644
--- a/include/drm-uapi/xe_drm.h
+++ b/include/drm-uapi/xe_drm.h
@@ -983,6 +983,8 @@ struct drm_xe_vm_create {
#define DRM_XE_VM_CREATE_FLAG_SCRATCH_PAGE (1 << 0)
#define DRM_XE_VM_CREATE_FLAG_LR_MODE (1 << 1)
#define DRM_XE_VM_CREATE_FLAG_FAULT_MODE (1 << 2)
+#define DRM_XE_VM_CREATE_FLAG_NO_VM_OVERCOMMIT (1 << 3)
+
/** @flags: Flags */
__u32 flags;
--
2.52.0
next prev parent reply other threads:[~2026-03-02 14:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:00 [PATCH i-g-t v2 0/2] test/intel/xe_vm: Add overcommit and no‑overcommit handling tests Sobin Thomas
2026-03-02 14:00 ` Sobin Thomas [this message]
2026-03-03 4:01 ` [PATCH v2 i-g-t 1/2] drm-uapi/xe: Add support for No Overcommit flag Sharma, Nishit
2026-03-04 12:44 ` Kamil Konieczny
2026-03-02 14:00 ` [PATCH v2 i-g-t 2/2] tests/intel/xe_vm: Add support for overcommit tests Sobin Thomas
2026-03-03 13:50 ` ✓ i915.CI.BAT: success for test/intel/xe_vm: Add overcommit and no‑overcommit handling tests (rev2) Patchwork
2026-03-03 13:52 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-03 22:04 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-03 22:33 ` ✓ Xe.CI.FULL: success " 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=20260302140010.1009564-2-sobin.thomas@intel.com \
--to=sobin.thomas@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=nishit.sharma@intel.com \
--cc=thomas.hellstrom@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