From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: thomas.hellstrom@intel.com, nishit.sharma@intel.com,
Sobin Thomas <sobin.thomas@intel.com>
Subject: [PATCH i-g-t 0/2] test/intel/xe_vm: Add overcommit and no‑overcommit handling tests
Date: Thu, 12 Feb 2026 19:03:01 +0000 [thread overview]
Message-ID: <20260212190305.804221-1-sobin.thomas@intel.com> (raw)
This series adds coverage to xe_vm test by adding over commit test in fault mode and
non fault mode.
Also added support to test the no overcommit flag (DRM_XE_VM_CREATE_NO_VM_OVERCOMMIT)
Sobin Thomas (2):
tests/intel/xe_vm: overcommit tests for fault-mode and non-fault-mode
VMs
test/intel/xe_vm: Test to check no overcommit flag in fault mode
include/drm-uapi/xe_drm.h | 1 +
tests/intel/xe_vm.c | 634 +++++++++++++++++++++++++++++++++++++-
2 files changed, 630 insertions(+), 5 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-12 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 19:03 Sobin Thomas [this message]
2026-02-12 19:03 ` [PATCH i-g-t 1/2] tests/intel/xe_vm: overcommit tests for fault-mode and non-fault-mode VMs Sobin Thomas
2026-02-12 19:03 ` [PATCH i-g-t 2/2] test/intel/xe_vm: Test to check no overcommit flag in fault mode Sobin Thomas
2026-02-24 19:41 ` Kamil Konieczny
2026-02-12 21:19 ` ✗ Xe.CI.BAT: failure for test/intel/xe_vm: Add overcommit and no‑overcommit handling tests Patchwork
2026-02-12 21:37 ` ✓ i915.CI.BAT: success " Patchwork
2026-02-13 0:58 ` ✗ i915.CI.Full: failure " Patchwork
2026-02-13 23:52 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-17 13:57 ` [PATCH i-g-t 0/2] " Hellstrom, Thomas
2026-02-17 14:06 ` Hellstrom, Thomas
-- strict thread matches above, loose matches on Subject: below --
2026-02-12 17:25 Sobin Thomas
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=20260212190305.804221-1-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 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.