Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: <intel-gfx@lists.freedesktop.org>,
	Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: Re: [PATCH] drm/i915/perf: Update handling of MMIO triggered reports
Date: Fri, 22 Dec 2023 13:46:51 -0800	[thread overview]
Message-ID: <ZYYDxBX0AIsX/H+g@unerlige-ril> (raw)
In-Reply-To: <20231219000543.1087706-1-umesh.nerlige.ramappa@intel.com>

On Mon, Dec 18, 2023 at 04:05:43PM -0800, Umesh Nerlige Ramappa wrote:
>On XEHP platforms user is not able to find MMIO triggered reports in the
>OA buffer since i915 squashes the context ID fields. These context ID
>fields hold the MMIO trigger markers.
>
>Update logic to not squash the context ID fields of MMIO triggered
>reports.
>
>Fixes: cba94bbcff08 ("drm/i915/perf: Determine context valid in OA reports")
>Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>---

>Fi.CI.IGT failures.
>
>Possible new issues
>Here are the unknown changes that may have been introduced in Patchwork_127946v2_full:
>
>IGT changes
>Possible regressions
>igt@gem_exec_suspend@basic-s3-devices@smem:
>shard-mtlp: NOTRUN -> ABORT
>
>igt@i915_selftest@live@gt_pm:
>shard-rkl: PASS -> DMESG-FAIL

The above are unrelated and do not exercise the code path that has the fix.

Thanks,
Umesh

>
>Known issues

      parent reply	other threads:[~2023-12-22 21:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  0:05 [PATCH] drm/i915/perf: Update handling of MMIO triggered reports Umesh Nerlige Ramappa
2023-12-19  4:57 ` ✗ Fi.CI.BAT: failure for " Patchwork
2023-12-20 17:31   ` Umesh Nerlige Ramappa
2023-12-19  5:28 ` [PATCH] " Dixit, Ashutosh
2023-12-19  5:48   ` Dixit, Ashutosh
2023-12-19  6:07     ` Umesh Nerlige Ramappa
2023-12-19  7:13       ` Dixit, Ashutosh
2023-12-22 21:46 ` Umesh Nerlige Ramappa [this message]

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=ZYYDxBX0AIsX/H+g@unerlige-ril \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=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