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 i-g-t v2 0/2] test/intel/xe_vm: Add overcommit and no‑overcommit handling tests
Date: Mon, 2 Mar 2026 14:00:08 +0000 [thread overview]
Message-ID: <20260302140010.1009564-1-sobin.thomas@intel.com> (raw)
This series introduces support for No Overcommit flags in the xe_uapi
and adds IGT tests to validate overcommit behaviour across different
VM modes.
Patch 1 updates the drm-uapi/xe flags in IGT to align with the
kernel changes that introduced NO_VM_OVERCOMMIT.
Patch 2 increase coverage to xe_vm tests by adding tests for
- Over-commit test in fault and non fault mode
- No-Over-Commit tests in fault mode
Sobin Thomas (2):
drm-uapi/xe: Add support for No Overcommit flag
tests/intel/xe_vm: Add support for overcommit tests
include/drm-uapi/xe_drm.h | 2 +
tests/intel/xe_vm.c | 517 ++++++++++++++++++++++++++++++++++++++
2 files changed, 519 insertions(+)
--
2.52.0
next reply other threads:[~2026-03-02 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 14:00 Sobin Thomas [this message]
2026-03-02 14:00 ` [PATCH v2 i-g-t 1/2] drm-uapi/xe: Add support for No Overcommit flag Sobin Thomas
2026-03-03 4:01 ` 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
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 11:04 [PATCH i-g-t v2 0/2] test/intel/xe_vm: Add overcommit and no‑overcommit handling tests 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=20260302140010.1009564-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.