From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Shekhar Chauhan <shekhar.chauhan@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] lib/xe/oa: Add support for 192B_MPEC8LL_NOA16 OAM format
Date: Thu, 16 Apr 2026 11:50:13 -0700 [thread overview]
Message-ID: <87zf327na2.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <9ff0775d-e568-46db-abb8-efad79ecb387@intel.com>
On Wed, 15 Apr 2026 21:31:23 -0700, Shekhar Chauhan wrote:
>
> > @@ -875,6 +875,30 @@ void intel_xe_perf_accumulate_reports(struct intel_xe_perf_accumulator *acc,
> > break;
> > + case XE_OAM_FORMAT_MPEC8u64_B8_C8:
> > + /* 64 bit timestamp */
> > + if (perf->devinfo.oa_timestamp_shift >= 0)
> > + deltas[idx++] += (end64[1] - start64[1]) << perf->devinfo.oa_timestamp_shift;
> > + else
> > + deltas[idx++] += (end64[1] - start64[1]) >> (-perf->devinfo.oa_timestamp_shift);
> > +
> > + /* 64 bit clock */
> > + deltas[idx++] += end64[3] - start64[3];
> > +
> > + /* 8x 64bit MPEC counters */
> > + for (i = 0; i < 8; i++)
> > + deltas[idx++] += end64[4 + i] - start64[4 + i];
> > +
> > +
> I feel the below increments are wrong. The added format is of 64bit.
> > /* 8x 32bit B counters */
> > + for (i = 0; i < 8; i++)
> > + accumulate_uint32(start + 16 + i, end + 16 + i, deltas + idx++);
> This should be "accumulate_uint32(start + 24 + i, end + 24 + i, deltas +
> idx++);"
> > +
> > + /* 8x 32bit C counters */
> > + for (i = 0; i < 8; i++)
> > + accumulate_uint32(start + 24 + i, end + 24 + i, deltas + idx++);
>
> And this, "accumulate_uint32(start + 32 + i, end + 32 + i, deltas + idx++);"
>
> I'm still new to this, so I can be wrong. Maybe help me understand. Other
> than this, patch looks fine to me.
Good catch, fixed in v2. Thanks!
next prev parent reply other threads:[~2026-04-16 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 21:52 [PATCH i-g-t] lib/xe/oa: Add support for 192B_MPEC8LL_NOA16 OAM format Ashutosh Dixit
2026-04-16 1:27 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-04-16 1:58 ` ✓ i915.CI.BAT: " Patchwork
2026-04-16 3:51 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-16 4:31 ` [PATCH i-g-t] " Shekhar Chauhan
2026-04-16 18:50 ` Dixit, Ashutosh [this message]
2026-04-16 11:39 ` ✗ i915.CI.Full: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-04-17 3:33 [PATCH i-g-t] " Ashutosh Dixit
2026-04-17 5:35 ` Shekhar Chauhan
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=87zf327na2.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=shekhar.chauhan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.