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 1/4] tests/intel/xe_oa: Fix report dumps in sanity check
Date: Sat, 23 Aug 2025 11:25:07 -0700 [thread overview]
Message-ID: <87tt1xyjy4.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20250823003401.109978-7-umesh.nerlige.ramappa@intel.com>
On Fri, 22 Aug 2025 17:34:03 -0700, Umesh Nerlige Ramappa wrote:
>
Hi Umesh,
> Fix report dumps in sanity check to dump the right amount of dwords.
>
> Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
> ---
> tests/intel/xe_oa.c | 6 ++----
> 1 file changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/tests/intel/xe_oa.c b/tests/intel/xe_oa.c
> index 63b59028fc5d..35d25150ec7d 100644
> --- a/tests/intel/xe_oa.c
> +++ b/tests/intel/xe_oa.c
> @@ -1052,8 +1052,8 @@ static void pec_sanity_check_reports(const u32 *report0, const u32 *report1,
> return;
> }
>
> - dump_report(report0, set->perf_raw_size, "pec_report0");
> - dump_report(report1, set->perf_raw_size, "pec_report1");
> + dump_report(report0, set->perf_raw_size / 4, "pec_report0");
> + dump_report(report1, set->perf_raw_size / 4, "pec_report1");
This is correct.
>
> pec_sanity_check(report0, report1, set);
> }
> @@ -1471,8 +1471,6 @@ read_2_oa_reports(int format_id,
> break;
> }
>
> - dump_report(report, format_size / 4, "oa-formats");
> -
Not sure about this. Could you move this to a different patch with
justification, if it's needed? I think this is there to dump Xe1 reports,
which pec_sanity_check_reports() will not dump, though maybe for Xe2 it
double dumps? I'd rather have more data there for debug, rather than data
missing.
> igt_debug("read report: reason = %x, timestamp = %"PRIx64", exponent mask=%x\n",
> report[0], oa_timestamp(report, format_id), exponent_mask);
>
> --
> 2.43.0
>
Thanks.
--
Ashutosh
next prev parent reply other threads:[~2025-08-23 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 0:34 [PATCH i-g-t 0/4] IGT xe_oa fixes, debug and new test Umesh Nerlige Ramappa
2025-08-23 0:34 ` [PATCH i-g-t 1/4] tests/intel/xe_oa: Fix report dumps in sanity check Umesh Nerlige Ramappa
2025-08-23 18:25 ` Dixit, Ashutosh [this message]
2025-08-26 0:38 ` Umesh Nerlige Ramappa
2025-08-23 0:34 ` [PATCH i-g-t 2/4] tests/intel/xe_oa: Fix waiting for mmaped reports Umesh Nerlige Ramappa
2025-08-23 18:47 ` Dixit, Ashutosh
2025-08-23 0:34 ` [PATCH i-g-t 3/4] tests/intel/xe_oa: Add a test for tail address wrap Umesh Nerlige Ramappa
2025-08-25 18:03 ` Dixit, Ashutosh
2025-08-26 0:58 ` Umesh Nerlige Ramappa
2025-08-26 1:06 ` Dixit, Ashutosh
2025-08-23 0:34 ` [PATCH i-g-t 4/4] tests/intel/xe_oa: Add an option to capture ftrace Umesh Nerlige Ramappa
2025-08-23 19:01 ` Dixit, Ashutosh
2025-08-25 17:18 ` Dixit, Ashutosh
2025-08-26 0:47 ` 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=87tt1xyjy4.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox