From: Francois Dugast <francois.dugast@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Francois Dugast <francois.dugast@intel.com>
Subject: [PATCH i-g-t 0/5] Stress copy engines during render
Date: Wed, 5 Mar 2025 10:06:10 +0100 [thread overview]
Message-ID: <20250305090743.16894-1-francois.dugast@intel.com> (raw)
This series uses existing BLT copy code to stress the copy engines with many
jobs in parallel, while measuring the impact on the execution duration of a
rendering job. This has been tested on BMG, where a typical run looks like
this:
IGT-Version: 1.30-gd625bfd4f (x86_64) (Linux: 6.14.0-rc3+ x86_64)
Using IGT_SRANDOM=1741100923 for randomisation
Opened device: /dev/dri/card0
Starting subtest: render-stress-0-copies
Render duration: avg = 3026116 ns, min = 2366875 ns, max = 6821519 ns
Subtest render-stress-0-copies: SUCCESS (0.326s)
Starting subtest: render-stress-1-copies
Render duration: avg = 2301721 ns, min = 2053743 ns, max = 3889482 ns
Subtest render-stress-1-copies: SUCCESS (0.276s)
Starting subtest: render-stress-2-copies
Render duration: avg = 7398805 ns, min = 1673659 ns, max = 261850405 ns
Subtest render-stress-2-copies: SUCCESS (0.535s)
Starting subtest: render-stress-4-copies
Render duration: avg = 17759307 ns, min = 2036909 ns, max = 780867436 ns
Subtest render-stress-4-copies: SUCCESS (1.059s)
Starting subtest: render-stress-16-copies
Render duration: avg = 79980375 ns, min = 2014429 ns, max = 3884022695 ns
Subtest render-stress-16-copies: SUCCESS (4.180s)
Francois Dugast (5):
lib/intel_blt: Promote blt_bo_copy()
lib/intel_blt: Allow forcing multiple runs in blt_mem_copy()
lib/intel_blt: Use blt_mem_copy() to stress copy functions
tests/intel/xe_render_copy: Expose render duration
tests/intel/xe_render_copy: Render under copy stress
lib/intel_blt.c | 86 +++++++++++---
lib/intel_blt.h | 6 +-
tests/intel/xe_copy_basic.c | 36 +-----
tests/intel/xe_render_copy.c | 212 ++++++++++++++++++++++++++++++++++-
4 files changed, 288 insertions(+), 52 deletions(-)
--
2.43.0
next reply other threads:[~2025-03-05 9:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 9:06 Francois Dugast [this message]
2025-03-05 9:06 ` [PATCH i-g-t 1/5] lib/intel_blt: Promote blt_bo_copy() Francois Dugast
2025-03-19 12:41 ` Thomas Hellström
2025-03-19 19:15 ` Zbigniew Kempczyński
2025-03-05 9:06 ` [PATCH i-g-t 2/5] lib/intel_blt: Allow forcing multiple runs in blt_mem_copy() Francois Dugast
2025-03-19 12:42 ` Thomas Hellström
2025-03-05 9:06 ` [PATCH i-g-t 3/5] lib/intel_blt: Use blt_mem_copy() to stress copy functions Francois Dugast
2025-03-19 12:46 ` Thomas Hellström
2025-03-19 19:21 ` Zbigniew Kempczyński
2025-03-05 9:06 ` [PATCH i-g-t 4/5] tests/intel/xe_render_copy: Expose render duration Francois Dugast
2025-03-19 12:48 ` Thomas Hellström
2025-03-05 9:06 ` [PATCH i-g-t 5/5] tests/intel/xe_render_copy: Render under copy stress Francois Dugast
2025-03-06 4:30 ` ✓ Xe.CI.BAT: success for Stress copy engines during render (rev2) Patchwork
2025-03-06 4:47 ` ✓ i915.CI.BAT: " Patchwork
2025-03-06 7:00 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-06 10:38 ` ✗ Xe.CI.Full: " Patchwork
2025-03-11 7:31 ` ✓ Xe.CI.BAT: success for Stress copy engines during render (rev3) Patchwork
2025-03-11 8:04 ` ✓ i915.CI.BAT: " Patchwork
2025-03-11 9:24 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-12 1:06 ` ✗ Xe.CI.Full: " Patchwork
2025-03-12 22:53 ` ✗ Xe.CI.BAT: failure for Stress copy engines during render (rev4) Patchwork
2025-03-12 23:04 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-12 23:46 ` ✓ i915.CI.Full: " Patchwork
2025-03-13 14:39 ` ✗ Xe.CI.Full: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-03-05 13:57 [PATCH i-g-t 0/5] Stress copy engines during render Francois Dugast
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=20250305090743.16894-1-francois.dugast@intel.com \
--to=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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