All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t v2 3/4] tests/intel/xe_oa: Add a test for tail address wrap
Date: Wed, 27 Aug 2025 19:30:45 -0700	[thread overview]
Message-ID: <85frdcjhyi.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <aK-XPcRQ27iGv66y@unerlige-desk.amr.corp.intel.com>

On Wed, 27 Aug 2025 16:39:41 -0700, Umesh Nerlige Ramappa wrote:
>
> Maybe we can hold off on this patch.
>
> It looks like when the issue occurs, we will not be able to read reports
> greater than fit_reports because the kmd will not be able to find valid
> reports in the OA buffer after the wrap (since the TAIL reg is out of
> sync).
>
> Will think of some other way to test this.

Yikes I forgot too. Maybe we can do something like this:

- Read fit_reports and make sure they are ok
- Now try to read extra_reports, or even a single report. Make sure we get
  stuck (maybe using poll()?). Timeout and send an interrupt signal to the
  blocked thread to unblock it.
- Now also check that the end of the buffer is non-zero

So yeah, definitely more involved.

Thanks.
--
Ashutosh

  reply	other threads:[~2025-08-28  2:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26 22:42 [PATCH i-g-t v2 0/4] IGT xe_oa fixes, debug and new test Umesh Nerlige Ramappa
2025-08-26 22:42 ` [PATCH i-g-t v2 1/4] tests/intel/xe_oa: Fix report dumps in sanity check Umesh Nerlige Ramappa
2025-08-26 23:49   ` Dixit, Ashutosh
2025-08-26 22:42 ` [PATCH i-g-t v2 2/4] tests/intel/xe_oa: Fix waiting for mmaped reports Umesh Nerlige Ramappa
2025-08-26 22:43 ` [PATCH i-g-t v2 3/4] tests/intel/xe_oa: Add a test for tail address wrap Umesh Nerlige Ramappa
2025-08-27 18:38   ` Dixit, Ashutosh
2025-08-27 23:39     ` Umesh Nerlige Ramappa
2025-08-28  2:30       ` Dixit, Ashutosh [this message]
2025-08-28  8:21         ` Kamil Konieczny
2025-08-26 22:43 ` [PATCH i-g-t v2 4/4] tests/intel/xe_oa: Add an option to capture register accesses in ftrace Umesh Nerlige Ramappa
2025-08-26 23:52   ` Dixit, Ashutosh
2025-08-29 22:34     ` Umesh Nerlige Ramappa
2025-08-26 23:22 ` ✓ Xe.CI.BAT: success for IGT xe_oa fixes, debug and new test (rev2) Patchwork
2025-08-26 23:29 ` ✓ i915.CI.BAT: " Patchwork
2025-08-27 10:51 ` ✗ Xe.CI.Full: failure " Patchwork
2025-08-27 11:39 ` ✗ i915.CI.Full: " 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=85frdcjhyi.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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 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.