Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sobin Thomas <sobin.thomas@intel.com>
To: igt-dev@lists.freedesktop.org, thomas.hellstrom@intel.com,
	nishit.sharma@intel.com
Cc: Sobin Thomas <sobin.thomas@intel.com>
Subject: [PATCH v3 i-g-t 1/1] tests/intel/xe_evict: overcommit tests for fault-mode and non-fault-mode VMs
Date: Thu, 22 Jan 2026 12:54:05 +0000	[thread overview]
Message-ID: <20260122125424.45139-1-sobin.thomas@intel.com> (raw)

The existing tests in xe_evict focus on system-wide memory allocation
across multiple processes. However, enhanced coverage for VRAM
overcommit handling in different VM modes was not there.

This change adds three new tests to verify VM overcommit handling.

 test_evict_oom(): Allocates BOs aggressively in a loop until
 VRAM overcommit occurs testing LR mode error handling.

 test_vm_nonfault_mode_overcommit() verifies that non-fault mode VMs
 properly reject overcommit attempts.

 test_vm_fault_mode_overcommit() validates that fault-mode VMs can
 handle memory pressure gracefully by touching pages to trigger page
 faults.

Sobin Thomas (1):
  tests/intel/xe_evict: overcommit tests for fault-mode and
    non-fault-mode VMs

 tests/intel/xe_evict.c | 310 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 310 insertions(+)

-- 
2.51.0


             reply	other threads:[~2026-01-22 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-22 12:54 Sobin Thomas [this message]
2026-01-22 12:54 ` [PATCH v3 i-g-t 1/1] tests/intel/xe_evict: overcommit tests for fault-mode and non-fault-mode VMs Sobin Thomas
2026-01-23  8:11   ` Sharma, Nishit
2026-01-22 16:39 ` ✗ Fi.CI.BUILD: failure for series starting with [v3,i-g-t,1/1] " 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=20260122125424.45139-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox