From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Matthew Brost <matthew.brost@intel.com>,
intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: daniele.ceraolospurio@intel.com, john.c.harrison@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915/selftests: Update live.evict to wait on requests / idle GPU after each loop
Date: Fri, 22 Oct 2021 08:11:55 +0200 [thread overview]
Message-ID: <7fa98234-73d5-69a7-d712-b3180614c873@linux.intel.com> (raw)
In-Reply-To: <20211021214040.33292-1-matthew.brost@intel.com>
On 10/21/21 23:40, Matthew Brost wrote:
> Update live.evict to wait on last request and idle GPU after each loop.
> This not only enhances the test to fill the GGTT on each engine class
> but also avoid timeouts from igt_flush_test when using GuC submission.
> igt_flush_test (idle GPU) can take a long time with GuC submission if
> losts of contexts are created due to H2G / G2H required to destroy
> contexts.
>
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>
LGTM,
Reviewed-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> .../gpu/drm/i915/selftests/i915_gem_evict.c | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/selftests/i915_gem_evict.c b/drivers/gpu/drm/i915/selftests/i915_gem_evict.c
> index f99bb0113726..7e0658a77659 100644
> --- a/drivers/gpu/drm/i915/selftests/i915_gem_evict.c
> +++ b/drivers/gpu/drm/i915/selftests/i915_gem_evict.c
> @@ -442,6 +442,7 @@ static int igt_evict_contexts(void *arg)
> /* Overfill the GGTT with context objects and so try to evict one. */
> for_each_engine(engine, gt, id) {
> struct i915_sw_fence fence;
> + struct i915_request *last = NULL;
>
> count = 0;
> onstack_fence_init(&fence);
> @@ -479,6 +480,9 @@ static int igt_evict_contexts(void *arg)
>
> i915_request_add(rq);
> count++;
> + if (last)
> + i915_request_put(last);
> + last = i915_request_get(rq);
> err = 0;
> } while(1);
> onstack_fence_fini(&fence);
> @@ -486,6 +490,21 @@ static int igt_evict_contexts(void *arg)
> count, engine->name);
> if (err)
> break;
> + if (last) {
> + if (i915_request_wait(last, 0, HZ) < 0) {
> + err = -EIO;
> + i915_request_put(last);
> + pr_err("Failed waiting for last request (on %s)",
> + engine->name);
> + break;
> + }
> + i915_request_put(last);
> + }
> + err = intel_gt_wait_for_idle(engine->gt, HZ * 3);
> + if (err) {
> + pr_err("Failed to idle GT (on %s)", engine->name);
> + break;
> + }
> }
>
> mutex_lock(&ggtt->vm.mutex);
next prev parent reply other threads:[~2021-10-22 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-21 21:40 [Intel-gfx] [PATCH] drm/i915/selftests: Update live.evict to wait on requests / idle GPU after each loop Matthew Brost
2021-10-22 2:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-22 6:11 ` Thomas Hellström [this message]
2021-10-22 6:47 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
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=7fa98234-73d5-69a7-d712-b3180614c873@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=matthew.brost@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