From: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
To: intel-gfx@lists.freedesktop.org, igt-dev@lists.freedesktop.org
Cc: Vinay Belgaumkar <vinay.belgaumkar@intel.com>,
Riana Tauro <riana.tauro@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH i-g-t v6 0/2] tests/intel/xe_pmu: Add PMU tests
Date: Mon, 27 Jan 2025 14:32:59 -0800 [thread overview]
Message-ID: <20250127223301.2819108-1-vinay.belgaumkar@intel.com> (raw)
Add utils and gt-c6 tests that utilize PMU counters.
Cc: Riana Tauro <riana.tauro@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Vinay Belgaumkar (2):
lib/igt_perf: Add utils to extract PMU event info
tests/xe/pmu: Add pmu tests
lib/igt_perf.c | 70 +++++++++++++++++
lib/igt_perf.h | 2 +
tests/intel/xe_pmu.c | 176 +++++++++++++++++++++++++++++++++++++++++++
tests/meson.build | 1 +
4 files changed, 249 insertions(+)
create mode 100644 tests/intel/xe_pmu.c
--
2.38.1
next reply other threads:[~2025-01-27 22:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 22:32 Vinay Belgaumkar [this message]
2025-01-27 22:33 ` [PATCH i-g-t v6 1/2] lib/igt_perf: Add utils to extract PMU event info Vinay Belgaumkar
2025-01-27 23:30 ` Lucas De Marchi
2025-01-29 10:57 ` Riana Tauro
2025-01-29 21:49 ` Belgaumkar, Vinay
2025-01-27 22:33 ` [PATCH i-g-t v6 2/2] tests/xe/pmu: Add pmu tests Vinay Belgaumkar
2025-01-27 23:56 ` Lucas De Marchi
2025-01-30 21:42 ` Belgaumkar, Vinay
2025-01-28 1:18 ` ✓ Xe.CI.BAT: success for tests/intel/xe_pmu: Add PMU tests (rev3) Patchwork
2025-01-28 1:26 ` ✓ i915.CI.BAT: " Patchwork
2025-01-28 14:20 ` ✗ i915.CI.Full: failure " Patchwork
2025-01-28 14:36 ` ✗ Xe.CI.Full: " 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=20250127223301.2819108-1-vinay.belgaumkar@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@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