From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH v3 0/2] Avoid reading OA reports before they land
Date: Fri, 2 Jun 2023 13:53:25 -0700 [thread overview]
Message-ID: <20230602205327.1542958-1-umesh.nerlige.ramappa@intel.com> (raw)
Fix OA issue seen on DG2 where parts of OA reports are zeroed out or
have stale values. This was due to the fact that rewind logic was not
being run when the tail pointer was aged. The series drops the complex
aging/aged logic and just checks the reports for validity.
rev1 - https://patchwork.freedesktop.org/series/118054/
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Umesh Nerlige Ramappa (2):
i915/perf: Drop the aging_tail logic in perf OA
i915/perf: Do not add ggtt offset to hw_tail
drivers/gpu/drm/i915/i915_perf.c | 76 ++++++++++----------------
drivers/gpu/drm/i915/i915_perf_types.h | 12 ----
2 files changed, 28 insertions(+), 60 deletions(-)
--
2.36.1
next reply other threads:[~2023-06-02 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 20:53 Umesh Nerlige Ramappa [this message]
2023-06-02 20:53 ` [Intel-gfx] [PATCH v3 1/2] i915/perf: Drop the aging_tail logic in perf OA Umesh Nerlige Ramappa
2023-06-02 21:53 ` Dixit, Ashutosh
2023-06-02 20:53 ` [Intel-gfx] [PATCH v3 2/2] i915/perf: Do not add ggtt offset to hw_tail Umesh Nerlige Ramappa
2023-06-02 22:07 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Avoid reading OA reports before they land Patchwork
2023-06-02 22:07 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-02 22:21 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-05 11:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20230602205327.1542958-1-umesh.nerlige.ramappa@intel.com \
--to=umesh.nerlige.ramappa@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