Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: adam.miszczak@linux.intel.com, jakub1.kolakowski@intel.com,
	lukasz.laguna@intel.com,
	Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Subject: [PATCH i-g-t 0/8] tests/intel/xe_sriov_scheduling: improve scheduling coverage
Date: Wed, 27 May 2026 22:56:33 +0200	[thread overview]
Message-ID: <20260527205644.2801165-1-marcin.bernatowicz@linux.intel.com> (raw)

Improve SR-IOV scheduling test coverage by adding default-enabled
fair-scheduling validation, broadening equal-throughput and
nonpreempt-engine-resets scenarios across GTs and both LOW/NORMAL
priorities, and strengthening result confidence with PMU-based checks
using engine-active-ticks and engine-total-ticks.

This series also includes earlier preparatory changes: timestamp helper,
scheduling priority support, and a const-correct helper signature update.

Marcin Bernatowicz (8):
  tests/intel/xe_sriov_scheduling: Use timestamp helper
  tests/intel/xe_sriov_scheduling: Add scheduling priority support
  tests/intel/xe_sriov_scheduling: Make sysfs_get_job_timeout_ms take
    const eci
  tests/intel/xe_sriov_scheduling: Add PMU-based verification helpers
  tests/intel/xe_sriov_scheduling: Raise min exec quantum to 2ms
  tests/intel/xe_sriov_scheduling: Refactor throughput_ratio and
    nonpreempt-engine-resets test
  tests/intel/xe_sriov_scheduling: Remove unused log_sample_values
    helper
  tests/intel/xe_sriov_scheduling: Add default fair scheduling test

 tests/intel/xe_sriov_scheduling.c | 1035 ++++++++++++++++++++++++-----
 1 file changed, 859 insertions(+), 176 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-05-27 20:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 20:56 Marcin Bernatowicz [this message]
2026-05-27 20:56 ` [PATCH i-g-t 1/8] tests/intel/xe_sriov_scheduling: Use timestamp helper Marcin Bernatowicz
2026-05-28 10:43   ` Kamil Konieczny
2026-05-27 20:56 ` [PATCH i-g-t 2/8] tests/intel/xe_sriov_scheduling: Add scheduling priority support Marcin Bernatowicz
2026-05-27 20:56 ` [PATCH i-g-t 3/8] tests/intel/xe_sriov_scheduling: Make sysfs_get_job_timeout_ms take const eci Marcin Bernatowicz
2026-05-27 20:56 ` [PATCH i-g-t 4/8] tests/intel/xe_sriov_scheduling: Add PMU-based verification helpers Marcin Bernatowicz
2026-05-27 20:56 ` [PATCH i-g-t 5/8] tests/intel/xe_sriov_scheduling: Raise min exec quantum to 2ms Marcin Bernatowicz
2026-05-27 20:56 ` [PATCH i-g-t 6/8] tests/intel/xe_sriov_scheduling: Refactor throughput_ratio and nonpreempt-engine-resets test Marcin Bernatowicz
2026-05-27 20:56 ` [PATCH i-g-t 7/8] tests/intel/xe_sriov_scheduling: Remove unused log_sample_values helper Marcin Bernatowicz
2026-05-27 20:56 ` [PATCH i-g-t 8/8] tests/intel/xe_sriov_scheduling: Add default fair scheduling test Marcin Bernatowicz
2026-05-28  0:01 ` ✓ Xe.CI.BAT: success for tests/intel/xe_sriov_scheduling: improve scheduling coverage Patchwork
2026-05-28  0:04 ` ✗ i915.CI.BAT: failure " Patchwork
2026-05-28 12:15 ` ✓ Xe.CI.FULL: success " 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=20260527205644.2801165-1-marcin.bernatowicz@linux.intel.com \
    --to=marcin.bernatowicz@linux.intel.com \
    --cc=adam.miszczak@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jakub1.kolakowski@intel.com \
    --cc=lukasz.laguna@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