Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 1/6] tests/intel/xe_oa: Rename check_reports to mmap_check_reports
Date: Mon, 14 Apr 2025 15:20:46 -0700	[thread overview]
Message-ID: <Z_2KPhY73pz979I0@unerlige-desk.amr.corp.intel.com> (raw)
In-Reply-To: <20250408181210.1052760-2-ashutosh.dixit@intel.com>

On Tue, Apr 08, 2025 at 11:12:05AM -0700, Ashutosh Dixit wrote:
>check_reports() is only used for checking reports for mmap OA buffer use
>case. Rename the function to the more specific name mmap_check_reports() to
>make the purpose of the function clearer and the function easier to find.
>
>Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>

Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>

>---
> tests/intel/xe_oa.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
>diff --git a/tests/intel/xe_oa.c b/tests/intel/xe_oa.c
>index 67acc74b32..a20120881a 100644
>--- a/tests/intel/xe_oa.c
>+++ b/tests/intel/xe_oa.c
>@@ -4246,8 +4246,8 @@ static void mmap_wait_for_periodic_reports(void *oa_vaddr, uint32_t n,
> 	}
> }
>
>-static void check_reports(void *oa_vaddr, uint32_t oa_size,
>-			  const struct drm_xe_engine_class_instance *hwe)
>+static void mmap_check_reports(void *oa_vaddr, uint32_t oa_size,
>+			       const struct drm_xe_engine_class_instance *hwe)
> {
> 	struct intel_xe_perf_metric_set *test_set = metric_set(hwe);
> 	uint64_t fmt = test_set->perf_oa_format;
>@@ -4279,7 +4279,7 @@ static void check_reports_from_mapped_buffer(const struct drm_xe_engine_class_in
> 	vaddr = map_oa_buffer(&size);
>
> 	mmap_wait_for_periodic_reports(vaddr, 10, hwe);
>-	check_reports(vaddr, size, hwe);
>+	mmap_check_reports(vaddr, size, hwe);
>
> 	munmap(vaddr, size);
> }
>@@ -4308,7 +4308,7 @@ static void closed_fd_and_unmapped_access(const struct drm_xe_engine_class_insta
> 	vaddr = map_oa_buffer(&size);
>
> 	mmap_wait_for_periodic_reports(vaddr, 10, hwe);
>-	check_reports(vaddr, size, hwe);
>+	mmap_check_reports(vaddr, size, hwe);
>
> 	munmap(vaddr, size);
> 	__perf_close(stream_fd);
>-- 
>2.48.1
>

  reply	other threads:[~2025-04-14 22:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 18:12 [PATCH i-g-t 0/6] Sanity check Xe2 PEC OA reports Ashutosh Dixit
2025-04-08 18:12 ` [PATCH i-g-t 1/6] tests/intel/xe_oa: Rename check_reports to mmap_check_reports Ashutosh Dixit
2025-04-14 22:20   ` Umesh Nerlige Ramappa [this message]
2025-04-08 18:12 ` [PATCH i-g-t 2/6] tests/intel/xe_oa: Fix oa_tick_delta Ashutosh Dixit
2025-04-14 22:21   ` Umesh Nerlige Ramappa
2025-04-08 18:12 ` [PATCH i-g-t 3/6] tests/intel/xe_oa: Sanity check PEC report data for TestOa metric set Ashutosh Dixit
2025-04-14 23:16   ` Umesh Nerlige Ramappa
2025-04-15 16:57     ` Dixit, Ashutosh
2025-04-16 16:20       ` Umesh Nerlige Ramappa
2025-04-22 19:42         ` Dixit, Ashutosh
2025-04-08 18:12 ` [PATCH i-g-t 4/6] tests/intel/xe_oa: Only sanity check timer PEC reports Ashutosh Dixit
2025-04-14 22:36   ` Umesh Nerlige Ramappa
2025-04-08 18:12 ` [PATCH i-g-t 5/6] tests/intel/xe_oa: Reduce test_non_zero_reason execution time Ashutosh Dixit
2025-04-14 22:40   ` Umesh Nerlige Ramappa
2025-04-15 16:49     ` Dixit, Ashutosh
2025-04-08 18:12 ` [PATCH i-g-t 6/6] tests/intel/xe_oa: Use TestOa metric set also for OAM Ashutosh Dixit
2025-04-14 22:41   ` Umesh Nerlige Ramappa
2025-04-14 23:22     ` Dixit, Ashutosh
2025-04-08 19:58 ` ✓ i915.CI.BAT: success for Sanity check Xe2 PEC OA reports Patchwork
2025-04-08 20:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-08 21:04 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-08 21:42 ` ✗ i915.CI.Full: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-04-22 19:34 [PATCH i-g-t 0/6] " Ashutosh Dixit
2025-04-22 19:34 ` [PATCH i-g-t 1/6] tests/intel/xe_oa: Rename check_reports to mmap_check_reports Ashutosh Dixit

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=Z_2KPhY73pz979I0@unerlige-desk.amr.corp.intel.com \
    --to=umesh.nerlige.ramappa@intel.com \
    --cc=ashutosh.dixit@intel.com \
    --cc=igt-dev@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