public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Hellstrom, Thomas" <thomas.hellstrom@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Thomas,  Sobin" <sobin.thomas@intel.com>
Cc: "Sharma, Nishit" <nishit.sharma@intel.com>
Subject: Re: [PATCH v4 i-g-t 0/1] tests/intel/xe_evict: overcommit tests for fault-mode and non-fault-mode VMs
Date: Thu, 5 Feb 2026 08:28:45 +0000	[thread overview]
Message-ID: <df2273c453d947192416925bfd25df4cf86c9cf1.camel@intel.com> (raw)
In-Reply-To: <20260205035041.413552-1-sobin.thomas@intel.com>

Hi, Thomas

On Thu, 2026-02-05 at 03:50 +0000, Sobin Thomas wrote:
> The existing tests in xe_evict focuses on system-wide memory
> allocation
> across multiple processes. However, OOM error handling in different
> VM
> modes was not being tested, and the previous test_svm_overcommit()
> had
> a critical bug that prevented proper overcommit scenarios.
> 
> Add three new tests to verify graceful OOM failure handling:
> 
> - test_evict_oom(): Allocates BOs aggressively in a loop until
>   OOM occurs. Tests error handling in LR mode and expects
>   -ENOSPC or -ENOMEM.
> 
> - test_vm_nonfault_mode_overcommit(): Verifies that non-fault mode
> VMs
>   properly reject overcommit attempts with -ENOSPC or -ENOMEM as
>   expected.
> 
> - test_vm_fault_mode_overcommit(): Validates that fault-mode VMs can
>   handle memory pressure gracefully by touching pages to trigger page
>   faults.
> 
> Signed-off-by: Sobin Thomas <sobin.thomas@intel.com>
> 
> Sobin Thomas (1):
>   tests/intel/xe_evict: overcommit tests for fault-mode and
>     non-fault-mode VMs
> 
>  tests/intel/xe_evict.c | 689
> ++++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 687 insertions(+), 2 deletions(-)

What's the relation to the xe_vm@out-of-memory test? Couldn't we build
on and possibly extend that? (I also have a modification in the pipe to
test this modification:

https://patchwork.freedesktop.org/series/161148/

Thanks,
Thomas




  parent reply	other threads:[~2026-02-05  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05  3:50 [PATCH v4 i-g-t 0/1] tests/intel/xe_evict: overcommit tests for fault-mode and non-fault-mode VMs Sobin Thomas
2026-02-05  3:50 ` [PATCH v4 i-g-t 1/1] " Sobin Thomas
2026-02-05  5:54 ` ✓ Xe.CI.BAT: success for tests/intel/xe_evict: overcommit tests for fault-mode and non-fault-mode VMs (rev3) Patchwork
2026-02-05  6:09 ` ✓ i915.CI.BAT: " Patchwork
2026-02-05  8:28 ` Hellstrom, Thomas [this message]
2026-02-05 19:29 ` ✓ i915.CI.Full: " Patchwork
2026-02-05 22:41 ` ✓ Xe.CI.FULL: " 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=df2273c453d947192416925bfd25df4cf86c9cf1.camel@intel.com \
    --to=thomas.hellstrom@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=nishit.sharma@intel.com \
    --cc=sobin.thomas@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