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] i915/drm_fdinfo: Quiesce GPU prior to running some tests
Date: Wed, 02 Oct 2024 16:19:31 -0700 [thread overview]
Message-ID: <85ploi6qkc.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20241002212049.769042-1-umesh.nerlige.ramappa@intel.com>
On Wed, 02 Oct 2024 14:20:49 -0700, Umesh Nerlige Ramappa wrote:
>
> 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>
Reviewed-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
Not related to this patch but little bit confusing, since I thought
drm_fdinfo is driver/vendor agnostic. But this file is i915 specific?
Should probably be named i915_fdinfo.c? Or if it's in intel/ directory
should at least probably work for both i195 and xe? Anyway.
next prev parent reply other threads:[~2024-10-02 23:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:20 [PATCH i-g-t] i915/drm_fdinfo: Quiesce GPU prior to running some tests Umesh Nerlige Ramappa
2024-10-02 22:32 ` ✓ CI.xeBAT: success for " Patchwork
2024-10-02 22:39 ` ✓ Fi.CI.BAT: " Patchwork
2024-10-02 23:19 ` Dixit, Ashutosh [this message]
2024-10-03 22:04 ` [PATCH i-g-t] " 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=85ploi6qkc.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