From: Matthew Brost <matthew.brost@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [RFC 1/4] drm/xe/multi_queue: Remove redundant assignment in guc_exec_queue_run_job
Date: Thu, 23 Apr 2026 14:30:57 -0700 [thread overview]
Message-ID: <aeqPkQoS3oXu6tGE@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260423024954.1665095-7-niranjana.vishwanathapura@intel.com>
On Wed, Apr 22, 2026 at 07:49:53PM -0700, Niranjana Vishwanathapura wrote:
> The 'killed_or_banned_or_wedged = true' assignment is redundant
> since the variable is never read after that point.
>
> Assisted-by: GitHub Copilot:claude-sonnet-4.6
> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> drivers/gpu/drm/xe/xe_guc_submit.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index b1222b42174c..104e65913dff 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -1216,10 +1216,8 @@ guc_exec_queue_run_job(struct drm_sched_job *drm_job)
> if (xe_exec_queue_is_multi_queue_secondary(q)) {
> struct xe_exec_queue *primary = xe_exec_queue_multi_queue_primary(q);
>
> - if (exec_queue_killed_or_banned_or_wedged(primary)) {
> - killed_or_banned_or_wedged = true;
> + if (exec_queue_killed_or_banned_or_wedged(primary))
> goto run_job_out;
> - }
>
> if (!exec_queue_registered(primary))
> register_exec_queue(primary, GUC_CONTEXT_NORMAL);
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-04-23 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 2:49 [RFC 0/4] drm/xe/multi_queue: Handle lost message during VF migration Niranjana Vishwanathapura
2026-04-23 2:49 ` [RFC 1/4] drm/xe/multi_queue: Remove redundant assignment in guc_exec_queue_run_job Niranjana Vishwanathapura
2026-04-23 21:30 ` Matthew Brost [this message]
2026-04-23 2:49 ` [RFC 2/4] drm/xe/multi_queue: Refactor CGP_SYNC send path Niranjana Vishwanathapura
2026-04-23 21:32 ` Matthew Brost
2026-04-23 2:49 ` [RFC 3/4] drm/xe/multi_queue: Handle VF recovery in CGP_SYNC and queue registration paths Niranjana Vishwanathapura
2026-04-23 21:45 ` Matthew Brost
2026-04-23 2:49 ` [RFC 4/4] drm/xe/multi_queue: Add needs_cgp_sync mechanism for VF post-migration recovery Niranjana Vishwanathapura
2026-04-23 21:44 ` Matthew Brost
2026-04-23 2:55 ` ✗ CI.checkpatch: warning for drm/xe/multi_queue: Handle lost message during VF migration Patchwork
2026-04-23 2:57 ` ✓ CI.KUnit: success " Patchwork
2026-04-23 3:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-23 13:29 ` ✗ Xe.CI.FULL: 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=aeqPkQoS3oXu6tGE@gsse-cloud1.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=niranjana.vishwanathapura@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