From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Sobin Thomas <sobin.thomas@intel.com>, igt-dev@lists.freedesktop.org
Cc: nishit.sharma@intel.com
Subject: Re: [PATCH i-g-t 0/1] tests/xe_vm: Add oversubscribe concurrent bind stress test
Date: Mon, 23 Mar 2026 18:05:42 +0100 [thread overview]
Message-ID: <d51282450f3a4995afc39e3189e2dbac1fe880bb.camel@linux.intel.com> (raw)
In-Reply-To: <20260218164417.856114-1-sobin.thomas@intel.com>
Hi,
On Wed, 2026-02-18 at 16:44 +0000, Sobin Thomas wrote:
> Add an xe_vm subtest that oversubscribes VRAM and issues
> concurrent binds into a single VM (scratch-page mode) to
> reproduce the dma-resv/bind race found under memory pressure.
> Prior coverage lacked any case that combined multi-process bind
> pressure with VRAM oversubscription, so bind/submit could
> panic (NULL deref in xe_pt_stage_bind) instead of failing cleanly.
> The new test expects successful completion or ENOMEM/EDEADLK.
No need to add a cover-letter when there is only a single patch. Just
add all information in the patch cover-message.
Are you seeing an EDEADLK error? That sounds like a KMD bug.
Thanks,
Thomas
>
> Sobin Thomas (1):
> tests/xe_vm: Add oversubscribe concurrent bind stress
>
> tests/intel/xe_vm.c | 421
> ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 421 insertions(+)
prev parent reply other threads:[~2026-03-23 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 16:44 [PATCH i-g-t 0/1] tests/xe_vm: Add oversubscribe concurrent bind stress test Sobin Thomas
2026-02-18 16:44 ` [PATCH i-g-t 1/1] " Sobin Thomas
2026-02-19 10:43 ` Sharma, Nishit
2026-03-05 3:25 ` Thomas, Sobin
2026-02-25 16:38 ` Kamil Konieczny
2026-03-23 17:37 ` Thomas Hellström
2026-02-18 18:09 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-02-18 18:17 ` ✓ i915.CI.BAT: " Patchwork
2026-02-18 20:20 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-18 20:42 ` ✗ i915.CI.Full: " Patchwork
2026-03-23 17:05 ` Thomas Hellström [this message]
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=d51282450f3a4995afc39e3189e2dbac1fe880bb.camel@linux.intel.com \
--to=thomas.hellstrom@linux.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