From: Matthew Brost <matthew.brost@intel.com>
To: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [RFC 3/4] drm/xe/multi_queue: Handle VF recovery in CGP_SYNC and queue registration paths
Date: Thu, 23 Apr 2026 14:45:00 -0700 [thread overview]
Message-ID: <aeqS3BhpXny9q0Dw@gsse-cloud1.jf.intel.com> (raw)
In-Reply-To: <20260423024954.1665095-9-niranjana.vishwanathapura@intel.com>
On Wed, Apr 22, 2026 at 07:49:55PM -0700, Niranjana Vishwanathapura wrote:
> In xe_guc_exec_queue_group_cgp_sync(), add vf_recovery(guc) as a wake
> condition on the wait_event_timeout() so VF migration does not cause a
> spurious timeout. Adjust the error check to only treat a timeout as an
> error when VF recovery is not in progress.
>
> 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 | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> index 4171eff4e8ad..0e857ef06611 100644
> --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> @@ -827,13 +827,12 @@ static void xe_guc_exec_queue_group_cgp_sync(struct xe_guc *guc,
> * Hence, no locking is required here.
> * Wait for any pending CGP_SYNC_DONE response before updating the
> * CGP page and sending CGP_SYNC message.
> - *
> - * FIXME: Support VF migration
> */
> ret = wait_event_timeout(guc->ct.wq,
> !READ_ONCE(group->sync_pending) ||
> - xe_guc_read_stopped(guc), HZ);
> - if (!ret || xe_guc_read_stopped(guc)) {
> + xe_guc_read_stopped(guc) ||
> + vf_recovery(guc), HZ);
> + if ((!ret && !vf_recovery(guc)) || xe_guc_read_stopped(guc)) {
> /* CGP_SYNC failed. Reset gt, cleanup the group */
> xe_gt_warn(guc_to_gt(guc), "Wait for CGP_SYNC_DONE response failed!\n");
> set_exec_queue_group_banned(q);
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-04-23 21:45 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
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 [this message]
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=aeqS3BhpXny9q0Dw@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