From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Subject: [PATCH i-g-t 0/5] OA: Run MMIO trigger tests on all OA units
Date: Tue, 25 Nov 2025 19:50:07 -0800 [thread overview]
Message-ID: <20251126035012.12967-1-ashutosh.dixit@intel.com> (raw)
Ashutosh Dixit (5):
tests/intel/xe_oa: Drop oa-unit-exclusive-stream-exec-q
drm-uapi/xe: Sync with DRM_XE_OA_CAPS_OA_UNIT_GT_ID definition
tests/intel/xe_oa: Return hwe from same gt from oa_unit_engine()
tests/intel/xe_oa: Run mmio-trigger tests on all OA units
tests/intel/xe_oa: Use separate oa unit variables for caps and
iterator
include/drm-uapi/xe_drm.h | 27 ++++-
tests/intel/xe_oa.c | 205 ++++++++++++++++++++++----------------
2 files changed, 146 insertions(+), 86 deletions(-)
--
2.48.1
next reply other threads:[~2025-11-26 3:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 3:50 Ashutosh Dixit [this message]
2025-11-26 3:50 ` [PATCH i-g-t 1/5] tests/intel/xe_oa: Drop oa-unit-exclusive-stream-exec-q Ashutosh Dixit
2025-12-02 21:32 ` Umesh Nerlige Ramappa
2025-11-26 3:50 ` [PATCH i-g-t 2/5] drm-uapi/xe: Sync with DRM_XE_OA_CAPS_OA_UNIT_GT_ID definition Ashutosh Dixit
2025-11-27 17:24 ` Kamil Konieczny
2025-11-26 3:50 ` [PATCH i-g-t 3/5] tests/intel/xe_oa: Return hwe from same gt from oa_unit_engine() Ashutosh Dixit
2025-11-26 3:50 ` [PATCH i-g-t 4/5] tests/intel/xe_oa: Run mmio-trigger tests on all OA units Ashutosh Dixit
2025-12-02 21:37 ` Umesh Nerlige Ramappa
2025-11-26 3:50 ` [PATCH i-g-t 5/5] tests/intel/xe_oa: Use separate oa unit variables for caps and iterator Ashutosh Dixit
2025-12-02 21:59 ` Umesh Nerlige Ramappa
2025-11-26 4:27 ` ✓ Xe.CI.BAT: success for OA: Run MMIO trigger tests on all OA units Patchwork
2025-11-26 4:41 ` ✓ i915.CI.BAT: " Patchwork
2025-11-26 7:27 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-26 15:01 ` ✗ i915.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=20251126035012.12967-1-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=umesh.nerlige.ramappa@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;
as well as URLs for NNTP newsgroup(s).