From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v5 0/4] lib/xe_spin: introduced fixed duration xe_spin
Date: Fri, 8 Sep 2023 17:12:56 +0000 [thread overview]
Message-ID: <20230908171300.2749840-1-marcin.bernatowicz@linux.intel.com> (raw)
Introduced struct xe_spin_opts for xe_spin initialization,
adjusted tests to new xe_spin_init signature.
Extended spinner with fixed duration capability. It allows
to prepare fixed duration (ex. 10ms) workloads and take workloads/second
measurements, a handy utility for scheduling tests.
Basic test for xe_spin with fixed duration.
v2: - added asserts in div64_u64_round_up, duration_to_ctx_ticks,
simplified loop_addr (Zbyszek)
- added xe_spin_init_opts macro (Zbyszek)
- corrected patch title (Kamil)
- Added assert for expected spinner duration. (Zbyszek)
A median of 5x100ms spins duration is computed, which should
satisfy CI runs, although better accuracy is achieved with
disabled logging (echo 0 > /sys/module/drm/parameters/debug).
v3: - extracted xe_spin_opts to separate patch (Kamil)
- div64_u64_round_up assert on overflow (Kamil)
- enum indentation cleanup in xe_spin.c (Kamil)
v4: - checkpatch fixes (Kamil)
- corrected variables readability in xe_spin_fixed_duration (Zbyszek)
v5: - fixed subject line to describe the change
not the tool that found it (Kamil)
- fixed too long line warning
Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Marcin Bernatowicz (4):
lib/xe_spin: xe_spin_opts for xe_spin initialization
lib/xe_spin: fixed duration xe_spin capability
tests/xe_spin_batch: spin-fixed-duration
lib/xe_spin.c: fixed code style
lib/xe/xe_spin.c | 126 ++++++++++++++++++++++++++++-----
lib/xe/xe_spin.h | 27 ++++++-
tests/intel/xe_dma_buf_sync.c | 6 +-
tests/intel/xe_exec_balancer.c | 9 ++-
tests/intel/xe_exec_reset.c | 24 ++++---
tests/intel/xe_exec_threads.c | 7 +-
tests/intel/xe_spin_batch.c | 73 +++++++++++++++++++
tests/intel/xe_vm.c | 7 +-
8 files changed, 234 insertions(+), 45 deletions(-)
--
2.30.2
next reply other threads:[~2023-09-08 17:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 17:12 Marcin Bernatowicz [this message]
2023-09-08 17:12 ` [igt-dev] [PATCH i-g-t v5 1/4] lib/xe_spin: xe_spin_opts for xe_spin initialization Marcin Bernatowicz
2023-09-08 17:12 ` [igt-dev] [PATCH i-g-t v5 2/4] lib/xe_spin: fixed duration xe_spin capability Marcin Bernatowicz
2023-09-08 17:12 ` [igt-dev] [PATCH i-g-t v5 3/4] tests/xe_spin_batch: spin-fixed-duration Marcin Bernatowicz
2023-09-08 17:13 ` [igt-dev] [PATCH i-g-t v5 4/4] lib/xe_spin.c: fixed code style Marcin Bernatowicz
2023-09-08 19:09 ` [igt-dev] ✓ CI.xeBAT: success for lib/xe_spin: introduced fixed duration xe_spin (rev4) Patchwork
2023-09-08 19:18 ` [igt-dev] ✗ Fi.CI.BAT: failure " Patchwork
2023-09-11 7:50 ` Bernatowicz, Marcin
2023-09-13 9:39 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-09-13 11:32 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-09-13 12:28 ` Bernatowicz, Marcin
2023-09-13 12:50 ` Bernatowicz, Marcin
2023-09-13 13:20 ` Yedireswarapu, SaiX Nandan
2023-09-13 13:02 ` 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=20230908171300.2749840-1-marcin.bernatowicz@linux.intel.com \
--to=marcin.bernatowicz@linux.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