From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 6/6] tests/intel/xe_oa: Use TestOa metric set also for OAM
Date: Mon, 14 Apr 2025 16:22:33 -0700 [thread overview]
Message-ID: <851ptus4zq.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <Z_2PEiclcjnk6STY@unerlige-desk.amr.corp.intel.com>
On Mon, 14 Apr 2025 15:41:22 -0700, Umesh Nerlige Ramappa wrote:
>
> On Tue, Apr 08, 2025 at 11:12:10AM -0700, Ashutosh Dixit wrote:
> > The only means available for testing OA data is the TestOa metric set, so
> > use that also for media OA.
> >
> > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> yeah, TestOa of OAM should be good enough.
>
> Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Unfortunately, looks like TestOa does *not* work for OAM, the counters are
not incrementing by gpu_ticks etc. So this patch needs to be dropped. Thanks!
>
>
> > ---
> > tests/intel/xe_oa.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tests/intel/xe_oa.c b/tests/intel/xe_oa.c
> > index f3ce37ff5a..0914054460 100644
> > --- a/tests/intel/xe_oa.c
> > +++ b/tests/intel/xe_oa.c
> > @@ -338,7 +338,7 @@ static struct intel_xe_perf_metric_set *metric_set(const struct drm_xe_engine_cl
> > else if ((hwe->engine_class == DRM_XE_ENGINE_CLASS_VIDEO_DECODE ||
> > hwe->engine_class == DRM_XE_ENGINE_CLASS_VIDEO_ENHANCE) &&
> > HAS_OAM(devid))
> > - test_set_name = "MediaSet1";
> > + test_set_name = "TestOa";
> > else
> > igt_assert(!"reached");
> >
> > --
> > 2.48.1
> >
next prev parent reply other threads:[~2025-04-14 23:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 18:12 [PATCH i-g-t 0/6] Sanity check Xe2 PEC OA reports Ashutosh Dixit
2025-04-08 18:12 ` [PATCH i-g-t 1/6] tests/intel/xe_oa: Rename check_reports to mmap_check_reports Ashutosh Dixit
2025-04-14 22:20 ` Umesh Nerlige Ramappa
2025-04-08 18:12 ` [PATCH i-g-t 2/6] tests/intel/xe_oa: Fix oa_tick_delta Ashutosh Dixit
2025-04-14 22:21 ` Umesh Nerlige Ramappa
2025-04-08 18:12 ` [PATCH i-g-t 3/6] tests/intel/xe_oa: Sanity check PEC report data for TestOa metric set Ashutosh Dixit
2025-04-14 23:16 ` Umesh Nerlige Ramappa
2025-04-15 16:57 ` Dixit, Ashutosh
2025-04-16 16:20 ` Umesh Nerlige Ramappa
2025-04-22 19:42 ` Dixit, Ashutosh
2025-04-08 18:12 ` [PATCH i-g-t 4/6] tests/intel/xe_oa: Only sanity check timer PEC reports Ashutosh Dixit
2025-04-14 22:36 ` Umesh Nerlige Ramappa
2025-04-08 18:12 ` [PATCH i-g-t 5/6] tests/intel/xe_oa: Reduce test_non_zero_reason execution time Ashutosh Dixit
2025-04-14 22:40 ` Umesh Nerlige Ramappa
2025-04-15 16:49 ` Dixit, Ashutosh
2025-04-08 18:12 ` [PATCH i-g-t 6/6] tests/intel/xe_oa: Use TestOa metric set also for OAM Ashutosh Dixit
2025-04-14 22:41 ` Umesh Nerlige Ramappa
2025-04-14 23:22 ` Dixit, Ashutosh [this message]
2025-04-08 19:58 ` ✓ i915.CI.BAT: success for Sanity check Xe2 PEC OA reports Patchwork
2025-04-08 20:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-08 21:04 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-08 21:42 ` ✗ 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=851ptus4zq.wl-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