From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: Lionel G Landwerlin <lionel.g.landwerlin@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/perf: Determine context valid in OA reports
Date: Thu, 15 Jun 2023 22:33:24 -0700 [thread overview]
Message-ID: <87v8fox97f.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20230616013850.611281-1-umesh.nerlige.ramappa@intel.com>
On Thu, 15 Jun 2023 18:38:50 -0700, Umesh Nerlige Ramappa wrote:
>
Hi Umesh,
> When supporting OA for TGL, it was seen that the context valid bit in
> the report ID was not defined, however revisiting the spec seems to have
> this bit defined. The bit is used to determine if a context is valid on
> a context switch and is essential to determine active and idle periods
> for a context. Re-enable the context valid bit for gen12 platforms.
A Bspec reference here would be nice if available. Otherwise this is:
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> Fixes: 00a7f0d7155c ("drm/i915/tgl: Add perf support on TGL")
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> ---
> drivers/gpu/drm/i915/i915_perf.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_perf.c b/drivers/gpu/drm/i915/i915_perf.c
> index 0a111b281578..b5491a382bfd 100644
> --- a/drivers/gpu/drm/i915/i915_perf.c
> +++ b/drivers/gpu/drm/i915/i915_perf.c
> @@ -482,8 +482,7 @@ static void oa_report_id_clear(struct i915_perf_stream *stream, u32 *report)
> static bool oa_report_ctx_invalid(struct i915_perf_stream *stream, void *report)
> {
> return !(oa_report_id(stream, report) &
> - stream->perf->gen8_valid_ctx_bit) &&
> - GRAPHICS_VER(stream->perf->i915) <= 11;
> + stream->perf->gen8_valid_ctx_bit);
> }
>
> static u64 oa_timestamp(struct i915_perf_stream *stream, void *report)
> @@ -5096,6 +5095,7 @@ static void i915_perf_init_info(struct drm_i915_private *i915)
> perf->gen8_valid_ctx_bit = BIT(16);
> break;
> case 12:
> + perf->gen8_valid_ctx_bit = BIT(16);
> /*
> * Calculate offset at runtime in oa_pin_context for gen12 and
> * cache the value in perf->ctx_oactxctrl_offset.
> --
> 2.36.1
>
next prev parent reply other threads:[~2023-06-16 6:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 1:38 [Intel-gfx] [PATCH] drm/i915/perf: Determine context valid in OA reports Umesh Nerlige Ramappa
2023-06-16 4:04 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-06-16 5:33 ` Dixit, Ashutosh [this message]
2023-06-17 5:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/perf: Determine context valid in OA reports (rev2) Patchwork
2023-06-17 9:59 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 20:28 [Intel-gfx] [PATCH] drm/i915/perf: Determine context valid in OA reports Umesh Nerlige Ramappa
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=87v8fox97f.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lionel.g.landwerlin@linux.intel.com \
--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