From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: igt-dev@lists.freedesktop.org, Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: [PATCH i-g-t] i915/drm_fdinfo: Quiesce GPU prior to running some tests
Date: Wed, 2 Oct 2024 14:20:49 -0700 [thread overview]
Message-ID: <20241002212049.769042-1-umesh.nerlige.ramappa@intel.com> (raw)
Sometimes render is still running a remnant of a prior workload when we
expect it to be idle. This throws some tests off. Ensure that these
tests wait for a quiescent state prior to checking if render is idle.
Closes: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12179
Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
---
tests/intel/drm_fdinfo.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tests/intel/drm_fdinfo.c b/tests/intel/drm_fdinfo.c
index 45d17aaaa..b66ac9e1b 100644
--- a/tests/intel/drm_fdinfo.c
+++ b/tests/intel/drm_fdinfo.c
@@ -219,6 +219,8 @@ single(int gem_fd, const intel_ctx_t *ctx,
int spin_fd;
uint64_t ahnd;
+ gem_quiescent_gpu(gem_fd);
+
if (flags & TEST_BUSY)
igt_require(!gem_using_guc_submission(gem_fd));
@@ -374,6 +376,8 @@ most_busy_check_all(int gem_fd, const intel_ctx_t *ctx,
memset(busy_class, 0, sizeof(busy_class));
memset(tval, 0, sizeof(tval));
+ gem_quiescent_gpu(gem_fd);
+
for_each_ctx_engine(gem_fd, ctx, e_) {
if (e->class == e_->class && e->instance == e_->instance) {
continue;
--
2.38.1
next reply other threads:[~2024-10-02 21:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:20 Umesh Nerlige Ramappa [this message]
2024-10-02 22:32 ` ✓ CI.xeBAT: success for i915/drm_fdinfo: Quiesce GPU prior to running some tests Patchwork
2024-10-02 22:39 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-02 23:19 ` [PATCH i-g-t] " Dixit, Ashutosh
2024-10-03 22:04 ` Umesh Nerlige Ramappa
2024-10-14 14:47 ` Kamil Konieczny
2024-10-02 23:56 ` ✗ CI.xeFULL: failure for " Patchwork
2024-10-14 21:48 ` Umesh Nerlige Ramappa
2024-10-04 4:54 ` ✗ Fi.CI.IGT: " Patchwork
2024-10-14 21: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=20241002212049.769042-1-umesh.nerlige.ramappa@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