Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: <intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe/pf: Fix VF FLR synchronization between all GTs
Date: Mon, 27 Oct 2025 11:31:55 +0100	[thread overview]
Message-ID: <20251027103155.726gxggfkvilfiwd@intel.com> (raw)
In-Reply-To: <20251025124906.5264-1-michal.wajdeczko@intel.com>

Michal Wajdeczko <michal.wajdeczko@intel.com> wrote on sob [2025-paź-25 14:49:05 +0200]:
> If subsequent VF FLR request is triggered when previous VF FLR
> sequence is still being processed, we ignore it as not needed.
> 
> But in case of the multi-GT platforms, one GT may already finish
> its VF FLR processing and will start a new sequence, which includes
> new cross-GT synchronization point.  However, since other GT may
> be still busy with post-sync cleanup steps, this will put on hold
> this new FLR sequence, which might never finish due to lack of any
> future synchronization checkouts.
> 
> Add additional cross-GT FLR synchronization point when each GT
> ends processing its own FLR sequence.  This should also help to
> cover the case when one GT fails FLR processing before reaching
> the first synchronization point.
> 
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/6287
> Fixes: 2a8fcf7cc950 ("drm/xe/pf: Synchronize VF FLR between all GTs")
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c b/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> index 2e6bd3d1fe1d..9de05db1f090 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_pf_control.c
> @@ -997,6 +997,8 @@ static void pf_exit_vf_flr_wip(struct xe_gt *gt, unsigned int vfid)
>  		pf_escape_vf_state(gt, vfid, XE_GT_SRIOV_STATE_FLR_GUC_DONE);
>  		pf_escape_vf_state(gt, vfid, XE_GT_SRIOV_STATE_FLR_WAIT_GUC);
>  		pf_escape_vf_state(gt, vfid, XE_GT_SRIOV_STATE_FLR_SEND_START);
> +
> +		xe_sriov_pf_control_sync_flr(gt_to_xe(gt), vfid);
>  	}
>  }

Reviewed-by: Piotr Piórkowski <piotr.piorkowski@intel.com>

>  
> -- 
> 2.47.1
> 

-- 

      parent reply	other threads:[~2025-10-27 10:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-25 12:49 [PATCH] drm/xe/pf: Fix VF FLR synchronization between all GTs Michal Wajdeczko
2025-10-25 13:13 ` ✓ CI.KUnit: success for " Patchwork
2025-10-25 13:51 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-25 15:03 ` ✓ Xe.CI.Full: " Patchwork
2025-10-27 10:31 ` Piotr Piórkowski [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=20251027103155.726gxggfkvilfiwd@intel.com \
    --to=piotr.piorkowski@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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