From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: igt-dev@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH i-g-t 0/8] Add per-client engine utilization tests
Date: Sat, 22 Jun 2024 07:00:54 +0800 [thread overview]
Message-ID: <20240621230102.238397-1-umesh.nerlige.ramappa@intel.com> (raw)
From: root <root@xpumcyp04.jf.intel.com>
Port per client engine utilization tests from i915 to xe.
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Umesh Nerlige Ramappa (8):
tests/intel/xe_drm_fdinfo: Update basic test to include client
utilization
tests/intel/xe_drm_fdinfo: Add helper to read utilization for all
classes
tests/intel/xe_drm_fdinfo: Add helpers for spinning batches
tests/intel/xe_drm_fdinfo: Add single engine tests
tests/intel/xe_drm_fdinfo: Add tests to verify all class utilization
tests/intel/xe_drm_fdinfo: Add an iterator for virtual engines
tests/intel/xe_drm_fdinfo: Add tests for virtual engines
tests/intel/xe_drm_fdinfo: Add tests for parallel engines
tests/intel/xe_drm_fdinfo.c | 586 +++++++++++++++++++++++++++++++++++-
1 file changed, 579 insertions(+), 7 deletions(-)
--
2.34.1
next reply other threads:[~2024-06-21 23:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 23:00 Umesh Nerlige Ramappa [this message]
2024-06-21 23:00 ` [PATCH i-g-t 1/8] tests/intel/xe_drm_fdinfo: Update basic test to include client utilization Umesh Nerlige Ramappa
2024-07-01 16:27 ` Riana Tauro
2024-07-01 18:30 ` Umesh Nerlige Ramappa
2024-07-01 16:52 ` Lucas De Marchi
2024-06-21 23:00 ` [PATCH i-g-t 2/8] tests/intel/xe_drm_fdinfo: Add helper to read utilization for all classes Umesh Nerlige Ramappa
2024-06-21 23:00 ` [PATCH i-g-t 3/8] tests/intel/xe_drm_fdinfo: Add helpers for spinning batches Umesh Nerlige Ramappa
2024-07-01 16:57 ` Lucas De Marchi
2024-07-01 17:27 ` Umesh Nerlige Ramappa
2024-07-01 18:08 ` Lucas De Marchi
2024-06-21 23:00 ` [PATCH i-g-t 4/8] tests/intel/xe_drm_fdinfo: Add single engine tests Umesh Nerlige Ramappa
2024-07-01 17:35 ` Lucas De Marchi
2024-07-01 18:26 ` Umesh Nerlige Ramappa
2024-07-02 18:18 ` Umesh Nerlige Ramappa
2024-07-02 20:57 ` Umesh Nerlige Ramappa
2024-07-02 20:57 ` Lucas De Marchi
2024-06-21 23:00 ` [PATCH i-g-t 5/8] tests/intel/xe_drm_fdinfo: Add tests to verify all class utilization Umesh Nerlige Ramappa
2024-06-21 23:01 ` [PATCH i-g-t 6/8] tests/intel/xe_drm_fdinfo: Add an iterator for virtual engines Umesh Nerlige Ramappa
2024-06-21 23:01 ` [PATCH i-g-t 7/8] tests/intel/xe_drm_fdinfo: Add tests " Umesh Nerlige Ramappa
2024-06-21 23:01 ` [PATCH i-g-t 8/8] tests/intel/xe_drm_fdinfo: Add tests for parallel engines Umesh Nerlige Ramappa
2024-06-21 23:35 ` ✓ CI.xeBAT: success for Add per-client engine utilization tests Patchwork
2024-06-21 23:44 ` ✓ Fi.CI.BAT: " Patchwork
2024-06-22 0:40 ` ✓ CI.xeFULL: " Patchwork
2024-06-22 21:32 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-06-28 21:27 ` ✓ CI.xeBAT: success for Add per-client engine utilization tests (rev2) Patchwork
2024-06-28 21:37 ` ✓ Fi.CI.BAT: " Patchwork
2024-06-28 22:21 ` ✓ CI.xeFULL: " Patchwork
2024-06-29 22:53 ` ✗ Fi.CI.IGT: failure " 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=20240621230102.238397-1-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=lucas.demarchi@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