Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Bernatowicz, Marcin" <marcin.bernatowicz@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>,
	igt-dev@lists.freedesktop.org
Cc: adam.miszczak@linux.intel.com, lukasz.laguna@intel.com
Subject: Re: [PATCH i-g-t 0/2] benchmarks/gem_wsim: explicit VM create/assign + LR mode
Date: Fri, 17 Jul 2026 10:03:08 +0200	[thread overview]
Message-ID: <26e3b680-63d1-48c8-b5aa-b728650a8556@linux.intel.com> (raw)
In-Reply-To: <87842c6f-f1b1-4a85-94bf-195a4930c247@igalia.com>


On 7/15/2026 3:36 PM, Tvrtko Ursulin wrote:
>
> On 14/07/2026 16:12, Marcin Bernatowicz wrote:
>> This series extends gem_wsim VM management for Xe.
>>
>> Patch 1 adds explicit VM create/assign steps in workload descriptors:
>> V.N to create VM N and v.N.M to bind context M to VM N.
>>
>> Patch 2 adds c.N to enable compute/LR mode on selected VMs.
>> README is updated with syntax and VM usage examples.
>>
>> Marcin Bernatowicz (2):
>>    benchmarks/gem_wsim: add explicit VM create/assign steps
>>    benchmarks/gem_wsim: add compute/LR mode support for Xe VMs
>
> I see these two patches have my Suggested-by but to be honest I do not 
> remember any of it! :)

That's a very old thread on the first patches adjusting the tool to Xe: 
https://lore.kernel.org/all/431b9135-1c7c-cbf7-cc3a-f8d52ff1f015@linux.intel.com/ 
;)

>
> Can I use the opportunity to ask how is the status of the tool on xe? 
> Do working set and working set dependencies work for example?
It's used for basic/simple workloads on VMs (Virtual Machines) with 
passed-through SR-IOV VF devices in regular runs (we use the expected 
duration of repeated workloads).

Lately, it helped me investigate an RCS/CCS dependency issue: 
https://lore.kernel.org/all/20260708100616.1050537-1-marcin.bernatowicz@linux.intel.com/

So, I find it very useful for quick scheduling dependency checks without 
having to craft or adjust IGT tests.

I haven't looked at working set / working set dependencies on Xe yet :/

Regards,

marcin

>
> Regards,
>
> Tvrtko
>
>>   benchmarks/gem_wsim.c  | 310 ++++++++++++++++++++++++++++++++++++-----
>>   benchmarks/wsim/README |  32 +++++
>>   2 files changed, 311 insertions(+), 31 deletions(-)
>>
>

  reply	other threads:[~2026-07-17  8:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 15:12 [PATCH i-g-t 0/2] benchmarks/gem_wsim: explicit VM create/assign + LR mode Marcin Bernatowicz
2026-07-14 15:12 ` [PATCH i-g-t 1/2] benchmarks/gem_wsim: add explicit VM create/assign steps Marcin Bernatowicz
2026-07-16 14:27   ` Kamil Konieczny
2026-08-03  9:26   ` Adam Miszczak
2026-07-14 15:12 ` [PATCH i-g-t 2/2] benchmarks/gem_wsim: add compute/LR mode support for Xe VMs Marcin Bernatowicz
2026-08-03  9:27   ` Adam Miszczak
2026-07-14 20:26 ` ✗ Xe.CI.BAT: failure for benchmarks/gem_wsim: explicit VM create/assign + LR mode Patchwork
2026-07-14 20:39 ` ✗ i915.CI.BAT: " Patchwork
2026-07-15  4:17 ` ✗ Xe.CI.FULL: " Patchwork
2026-07-15 13:36 ` [PATCH i-g-t 0/2] " Tvrtko Ursulin
2026-07-17  8:03   ` Bernatowicz, Marcin [this message]
2026-07-17 12:09     ` Bernatowicz, Marcin
2026-07-17 12:32       ` Tvrtko Ursulin

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=26e3b680-63d1-48c8-b5aa-b728650a8556@linux.intel.com \
    --to=marcin.bernatowicz@linux.intel.com \
    --cc=adam.miszczak@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lukasz.laguna@intel.com \
    --cc=tvrtko.ursulin@igalia.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