From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 3/3] drm/i915/perf: Initialize gen12 OA buffer unconditionally
Date: Fri, 08 Sep 2023 18:24:16 -0700 [thread overview]
Message-ID: <87r0n8qgu7.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230909011626.1643734-4-ashutosh.dixit@intel.com>
On Fri, 08 Sep 2023 18:16:26 -0700, Ashutosh Dixit wrote:
>
Hi Umesh,
> From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>
> Correct values for OAR counters are still dependent on enabling the
> GEN12_OAG_OACONTROL_OA_COUNTER_ENABLE in OAG_OACONTROL. Enabling this
> bit means OAG unit will write reports to the OAG buffer, so
> initialize the OAG buffer unconditionally for all use cases.
>
> BSpec: 46822
>
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> ---
> drivers/gpu/drm/i915/i915_perf.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index 1347e4ec9dd5a..30cf37d6e79be 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -3032,12 +3032,12 @@ static void gen12_oa_enable(struct i915_perf_stream *stream)
> u32 val;
>
> /*
> - * If we don't want OA reports from the OA buffer, then we don't even
> - * need to program the OAG unit.
> + * BSpec: 46822
> + * Correct values for OAR counters are still dependent on enabling the
> + * GEN12_OAG_OACONTROL_OA_COUNTER_ENABLE in OAG_OACONTROL. Enabling this
> + * bit means OAG unit will write reports to the OAG buffer, so
> + * initialize the OAG buffer correctly.
> */
> - if (!(stream->sample_flags & SAMPLE_OA_REPORT))
> - return;
> -
> gen12_init_oa_buffer(stream);
>
> regs = __oa_regs(stream);
Looks like this should be needed, I can R-b it.
However, gen12_test_mi_rpc IGT says:
/* OA unit configuration:
* DRM_I915_PERF_PROP_SAMPLE_OA is no longer required for Gen12
* because the OAR unit increments counters only for the
* relevant context. No other parameters are needed since we do
* not rely on the OA buffer anymore to normalize the counter
* values.
*/
So gen12_test_mi_rpc doesn't set DRM_I915_PERF_PROP_SAMPLE_OA and also
seems to be passing in CI (don't see it but there seem to be no open
bugs). Thoughts?
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2023-09-09 1:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 1:16 [Intel-gfx] [PATCH 0/3] drm/i915/perf: A few fixes and enhancements Ashutosh Dixit
2023-09-09 1:16 ` [Intel-gfx] [PATCH 1/3] drm/i915/perf: Subtract gtt_offset from hw_tail Ashutosh Dixit
2023-09-13 1:25 ` Umesh Nerlige Ramappa
2023-09-13 2:20 ` Dixit, Ashutosh
2023-09-09 1:16 ` [Intel-gfx] [PATCH 2/3] drm/i915/perf: Remove gtt_offset from stream->oa_buffer.head/.tail Ashutosh Dixit
2023-09-13 1:36 ` Umesh Nerlige Ramappa
2023-09-09 1:16 ` [Intel-gfx] [PATCH 3/3] drm/i915/perf: Initialize gen12 OA buffer unconditionally Ashutosh Dixit
2023-09-09 1:24 ` Dixit, Ashutosh [this message]
2023-09-13 1:46 ` Umesh Nerlige Ramappa
2023-09-13 16:59 ` Dixit, Ashutosh
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=87r0n8qgu7.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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