From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Matthew Brost <matthew.brost@intel.com>,
Tomasz Lis <tomasz.lis@intel.com>
Subject: Re: [PATCH v2 1/2] drm/xe/vf: Avoid queuing migration recovery if queued or teardown is active
Date: Mon, 8 Dec 2025 22:11:51 +0100 [thread overview]
Message-ID: <2015cc97-e380-4ea7-902a-c674e55a39fc@intel.com> (raw)
In-Reply-To: <20251208072739.336647-5-satyanarayana.k.v.p@intel.com>
On 12/8/2025 8:27 AM, Satyanarayana K V P wrote:
> Ensure VF migration recovery work is only queued when no recovery is
> already queued and teardown is not in progress.
>
> Fixes: b47c0c07c350 ("drm/xe/vf: Teardown VF post migration worker on driver unload")
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Matthew Brost <matthew.brost@intel.com>
> Cc: Tomasz Lis <tomasz.lis@intel.com>
nit: subject is little too long, maybe just:
drm/xe/vf: Fix queuing of recovery work
but fix is fine, so
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
>
> ---
> V1 -> V2:
> - New commit (Machal W & Matt B)
> ---
> drivers/gpu/drm/xe/xe_gt_sriov_vf.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_vf.c b/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
> index 3c806c8e5f3e..47612e67d462 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
> @@ -781,7 +781,7 @@ static void vf_start_migration_recovery(struct xe_gt *gt)
>
> spin_lock(>->sriov.vf.migration.lock);
>
> - if (!gt->sriov.vf.migration.recovery_queued ||
> + if (!gt->sriov.vf.migration.recovery_queued &&
> !gt->sriov.vf.migration.recovery_teardown) {
> gt->sriov.vf.migration.recovery_queued = true;
> WRITE_ONCE(gt->sriov.vf.migration.recovery_inprogress, true);
next prev parent reply other threads:[~2025-12-08 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 7:27 [PATCH v2 0/2] Reset recovery_queued after issuing RESFIX_START Satyanarayana K V P
2025-12-08 7:27 ` [PATCH v2 1/2] drm/xe/vf: Avoid queuing migration recovery if queued or teardown is active Satyanarayana K V P
2025-12-08 21:11 ` Michal Wajdeczko [this message]
2025-12-08 21:14 ` Matthew Brost
2025-12-08 7:27 ` [PATCH v2 2/2] drm/xe/vf: Reset recovery_queued after issuing RESFIX_START Satyanarayana K V P
2025-12-08 21:16 ` Matthew Brost
2025-12-08 8:02 ` ✓ CI.KUnit: success for Reset recovery_queued after issuing RESFIX_START (rev2) Patchwork
2025-12-08 9:04 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-08 9:42 ` ✗ 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=2015cc97-e380-4ea7-902a-c674e55a39fc@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@intel.com \
--cc=satyanarayana.k.v.p@intel.com \
--cc=tomasz.lis@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