From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>
Subject: [PATCH i-g-t 0/2] tests/intel/xe_evict: Adapt the working set to memory size
Date: Wed, 26 Jun 2024 14:38:31 +0200 [thread overview]
Message-ID: <20240626123833.3164-1-thomas.hellstrom@linux.intel.com> (raw)
It turns out that xe_evict in the cm and thread mode is a very good test for
exhaustive eviction. But the test sometimes uses a working set that doesn't fit
in gpu-accessible memory and a total memory size that exceeds the available
system size. Attempt to fix that to avoid false failures. With these fixes
the test should pass unless in -cm mode or multithreaded mode. These require
fixes for exhaustive eviction in the xe kernel driver.
Thomas Hellström (2):
tests/intel/xe_evict: Reduce allocations to maximum working set
tests/intel/xe_evict: Reduce the "large" bo size for threaded eviction
tests/intel/xe_evict.c | 126 ++++++++++++++++++++++++++++++++---------
1 file changed, 99 insertions(+), 27 deletions(-)
--
2.44.0
next reply other threads:[~2024-06-26 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 12:38 Thomas Hellström [this message]
2024-06-26 12:38 ` [PATCH i-g-t 1/2] tests/intel/xe_evict: Reduce allocations to maximum working set Thomas Hellström
2024-06-27 6:29 ` Matthew Brost
2024-06-27 7:28 ` Thomas Hellström
2024-06-26 12:38 ` [PATCH i-g-t 2/2] tests/intel/xe_evict: Reduce the "large" bo size for threaded eviction Thomas Hellström
2024-06-27 6:34 ` Matthew Brost
2024-06-27 7:31 ` Thomas Hellström
2024-06-26 15:20 ` ✗ Fi.CI.BAT: failure for tests/intel/xe_evict: Adapt the working set to memory size Patchwork
2024-06-26 15:23 ` ✓ CI.xeBAT: success " Patchwork
2024-06-26 17:00 ` [PATCH i-g-t 0/2] " Matthew Brost
2024-06-26 21:02 ` ✓ CI.xeFULL: success for " 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=20240626123833.3164-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@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