From: "Das, Nirmoy" <nirmoy.das@linux.intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: don't hardcode BCS0 in guc_hang selftest
Date: Thu, 3 Nov 2022 10:10:20 +0100 [thread overview]
Message-ID: <2d6e7e7b-81dc-7ae3-8dbc-a5adb13c8b2e@linux.intel.com> (raw)
In-Reply-To: <20221102214310.2829310-1-daniele.ceraolospurio@intel.com>
LGTM Acked-by: Nirmoy Das <nirmoy.das@intel.com>
On 11/2/2022 10:43 PM, Daniele Ceraolo Spurio wrote:
> On MTL there are no BCS engines on the media GT, so we can't always use
> BCS0 in the test. There is no actual reason to use a BCS engine over an
> engine of a different class, so switch to using any available engine.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/selftest_guc_hangcheck.c | 8 +++++---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/uc/selftest_guc_hangcheck.c b/drivers/gpu/drm/i915/gt/uc/selftest_guc_hangcheck.c
> index 01f8cd3c3134..d91b58f70403 100644
> --- a/drivers/gpu/drm/i915/gt/uc/selftest_guc_hangcheck.c
> +++ b/drivers/gpu/drm/i915/gt/uc/selftest_guc_hangcheck.c
> @@ -35,11 +35,14 @@ static int intel_hang_guc(void *arg)
> struct i915_request *rq;
> intel_wakeref_t wakeref;
> struct i915_gpu_error *global = >->i915->gpu_error;
> - struct intel_engine_cs *engine;
> + struct intel_engine_cs *engine = intel_selftest_find_any_engine(gt);
> unsigned int reset_count;
> u32 guc_status;
> u32 old_beat;
>
> + if (!engine)
> + return 0;
> +
> ctx = kernel_context(gt->i915, NULL);
> if (IS_ERR(ctx)) {
> drm_err(>->i915->drm, "Failed get kernel context: %ld\n", PTR_ERR(ctx));
> @@ -48,14 +51,13 @@ static int intel_hang_guc(void *arg)
>
> wakeref = intel_runtime_pm_get(gt->uncore->rpm);
>
> - ce = intel_context_create(gt->engine[BCS0]);
> + ce = intel_context_create(engine);
> if (IS_ERR(ce)) {
> ret = PTR_ERR(ce);
> drm_err(>->i915->drm, "Failed to create spinner request: %d\n", ret);
> goto err;
> }
>
> - engine = ce->engine;
> reset_count = i915_reset_count(global);
>
> old_beat = engine->props.heartbeat_interval_ms;
next prev parent reply other threads:[~2022-11-03 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 21:43 [Intel-gfx] [PATCH] drm/i915/guc: don't hardcode BCS0 in guc_hang selftest Daniele Ceraolo Spurio
2022-11-02 23:42 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for " Patchwork
2022-11-03 0:02 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-11-03 0:34 ` [Intel-gfx] [PATCH] " John Harrison
2022-11-03 9:10 ` Das, Nirmoy [this message]
2022-11-03 10:30 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=2d6e7e7b-81dc-7ae3-8dbc-a5adb13c8b2e@linux.intel.com \
--to=nirmoy.das@linux.intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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