From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [PATCH] tests/xe: Add system_allocator test
Date: Wed, 16 Apr 2025 19:09:40 +0200 [thread overview]
Message-ID: <ac738d56a54052862f5e9fc74f905d05315c33c4.camel@linux.intel.com> (raw)
In-Reply-To: <20250416022040.355100-1-matthew.brost@intel.com>
Hi, Matt,
On Tue, 2025-04-15 at 19:20 -0700, Matthew Brost wrote:
> Test various uses of system allocator in single thread, multiple
> threads, and multiple processes.
>
> Features tested:
> - Malloc with various size
> - Mmap with various sizes and flags including file backed mappings
> - Mixing BO allocations with system allocator
> - Various page sizes
> - Dynamically freeing / unmapping memory
> - Sharing VM across threads
> - Faults racing on different hardware engines / GTs / Tiles
> - GPU faults and CPU faults racing
> - CPU faults on multiple threads racing
> - CPU faults on multiple process racing
> - GPU faults of memory not faulted in by CPU
> - Partial unmap of allocations
> - Attempting to unmap system allocations when GPU has mappings
> - Eviction of both system allocations and BOs
> - Forking child processes and reading data from VRAM
> - mremap data in VRAM
> - Protection changes
> - Multiple faults per execbuf
>
> Running on LNL, BMG, PVC 1 tile, and PVC 2 tile.
>
> v2:
> - Rebase
> - Fix memory allocation to not interfear with malloc (Thomas)
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Did you have a chance to look at the memory (or rather virtual
adddress) leaks on the tests as well?
With the old version it would exceed 1GB after some time, which I
believe caused some slowdown.
Unfortunately the igt library funcs also leaks memory so running the
test under valgrind was a bit noisy, but helped to some extent.
/Thomas
next prev parent reply other threads:[~2025-04-16 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 2:20 [PATCH] tests/xe: Add system_allocator test Matthew Brost
2025-04-16 17:09 ` Thomas Hellström [this message]
2025-04-16 18:36 ` Matthew Brost
2025-04-18 15:47 ` Francois Dugast
2025-04-18 19:44 ` Matthew Brost
2025-04-24 19:28 ` Francois Dugast
2025-04-24 19:46 ` Matthew Brost
-- strict thread matches above, loose matches on Subject: below --
2025-04-25 18:20 Matthew Brost
2024-10-16 3:04 Matthew Brost
2024-08-27 23:16 Matthew Brost
2024-08-21 1:41 Matthew Brost
2024-05-21 4:18 [PATCH] tests/xe: Add System Allocator test Matthew Brost
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=ac738d56a54052862f5e9fc74f905d05315c33c4.camel@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--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