From: Anshuman Gupta <anshuman.gupta@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] test/intel/perf_pmu: Dump drpc for correct gt
Date: Mon, 20 Nov 2023 20:00:22 +0530 [thread overview]
Message-ID: <20231120143022.4184274-1-anshuman.gupta@intel.com> (raw)
other-idle-gt rc6 test dumps drpc for wrong gt.
use gt, which has passed as function argument to
test_rc6 to dump drpc.
Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
---
tests/intel/perf_pmu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/intel/perf_pmu.c b/tests/intel/perf_pmu.c
index c6e6a8b77..80763af1d 100644
--- a/tests/intel/perf_pmu.c
+++ b/tests/intel/perf_pmu.c
@@ -1981,7 +1981,7 @@ test_rc6(int gem_fd, unsigned int gt, unsigned int num_gt, unsigned int flags)
}
}
- igt_require_f(wait_for_rc6(fd[0], 1, pmus, test_idx),
+ igt_require_f(wait_for_rc6(fd[0], 1, pmus, gt),
"failed to enter c6 \n%s\n", drpc = get_drpc(gem_fd, test_idx));
/* While idle check full RC6. */
@@ -2022,7 +2022,7 @@ test_rc6(int gem_fd, unsigned int gt, unsigned int num_gt, unsigned int flags)
}
}
- igt_require_f(wait_for_rc6(fd[0], 5, pmus, test_idx),
+ igt_require_f(wait_for_rc6(fd[0], 5, pmus, gt),
"failed to enter c6 \n%s\n", drpc = get_drpc(gem_fd, test_idx));
ts[0] = pmu_read_multi(fd[0], pmus, prev);
--
2.25.1
next reply other threads:[~2023-11-20 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 14:30 Anshuman Gupta [this message]
2023-11-20 20:27 ` [igt-dev] ✓ Fi.CI.BAT: success for test/intel/perf_pmu: Dump drpc for correct gt Patchwork
2023-11-20 21:20 ` [igt-dev] ✗ CI.xeBAT: failure " Patchwork
2023-11-22 12:32 ` [igt-dev] ✓ Fi.CI.BAT: success for test/intel/perf_pmu: Dump drpc for correct gt (rev2) Patchwork
2023-11-22 13:30 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-23 4:48 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-11-29 14:10 ` [igt-dev] [PATCH i-g-t] test/intel/perf_pmu: Dump drpc for correct gt Kamil Konieczny
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=20231120143022.4184274-1-anshuman.gupta@intel.com \
--to=anshuman.gupta@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