From: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Noop lrc_init_wa_ctx() on recent/future platforms
Date: Thu, 22 Sep 2022 13:46:08 +0530 [thread overview]
Message-ID: <YywZyOTQPGL+txP3@bala-ubuntu> (raw)
In-Reply-To: <20220907230841.1703574-1-lucas.demarchi@intel.com>
On 07.09.2022 16:08, Lucas De Marchi wrote:
> Except for graphics version 8 and 9, nothing is done in
> lrc_init_wa_ctx(). Assume this won't be needed on future platforms as
> well and remove the warning.
>
> Note that this function is not called for anything below version 8 since
> those don't use either guc or execlist, i.e. HAS_EXECLISTS() is false.
>
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
> drivers/gpu/drm/i915/gt/intel_lrc.c | 16 ++++------------
> 1 file changed, 4 insertions(+), 12 deletions(-)
Reviewed-by: Balasubramani Vivekanandan <balasubramani.vivekanandan@intel.com>
>
> diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c b/drivers/gpu/drm/i915/gt/intel_lrc.c
> index 070cec4ff8a4..43fa7b3422c4 100644
> --- a/drivers/gpu/drm/i915/gt/intel_lrc.c
> +++ b/drivers/gpu/drm/i915/gt/intel_lrc.c
> @@ -1695,24 +1695,16 @@ void lrc_init_wa_ctx(struct intel_engine_cs *engine)
> unsigned int i;
> int err;
>
> - if (!(engine->flags & I915_ENGINE_HAS_RCS_REG_STATE))
> + if (GRAPHICS_VER(engine->i915) >= 11 ||
> + !(engine->flags & I915_ENGINE_HAS_RCS_REG_STATE))
> return;
>
> - switch (GRAPHICS_VER(engine->i915)) {
> - case 12:
> - case 11:
> - return;
> - case 9:
> + if (GRAPHICS_VER(engine->i915) == 9) {
> wa_bb_fn[0] = gen9_init_indirectctx_bb;
> wa_bb_fn[1] = NULL;
> - break;
> - case 8:
> + } else if (GRAPHICS_VER(engine->i915) == 8) {
> wa_bb_fn[0] = gen8_init_indirectctx_bb;
> wa_bb_fn[1] = NULL;
> - break;
> - default:
> - MISSING_CASE(GRAPHICS_VER(engine->i915));
> - return;
> }
>
> err = lrc_create_wa_ctx(engine);
> --
> 2.37.2
>
prev parent reply other threads:[~2022-09-22 8:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 23:08 [Intel-gfx] [PATCH] drm/i915: Noop lrc_init_wa_ctx() on recent/future platforms Lucas De Marchi
2022-09-07 23:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-09-08 7:35 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-09-22 8:16 ` Balasubramani Vivekanandan [this message]
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=YywZyOTQPGL+txP3@bala-ubuntu \
--to=balasubramani.vivekanandan@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@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