Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Matthew Brost <matthew.brost@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/xe: Avoid PM wake reference during VF migration
Date: Wed, 22 Oct 2025 11:08:27 +0100	[thread overview]
Message-ID: <9b2419c8-efd0-41fc-98e4-f4324ac423f4@intel.com> (raw)
In-Reply-To: <20251022005538.828980-4-matthew.brost@intel.com>

On 22/10/2025 01:55, Matthew Brost wrote:
> Virtual Functions (VFs) do not use runtime PM. Avoid taking PM
> references during VF migration, as lockdep may get confused—VF migration
> occurs in the reclaim path, and waking a PM reference can trigger memory
> allocation warnings.
> 
> Signed-off-by: Matthew Brost <matthew.brost@intel.com>

Reviewed-by: Matthew Auld <matthew.auld@intel.com>

> ---
>   drivers/gpu/drm/xe/xe_gt_sriov_vf.c | 5 -----
>   1 file changed, 5 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt_sriov_vf.c b/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
> index 46518e629ba3..d0b102ab6ce8 100644
> --- a/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
> +++ b/drivers/gpu/drm/xe/xe_gt_sriov_vf.c
> @@ -31,7 +31,6 @@
>   #include "xe_lrc.h"
>   #include "xe_memirq.h"
>   #include "xe_mmio.h"
> -#include "xe_pm.h"
>   #include "xe_sriov.h"
>   #include "xe_sriov_vf.h"
>   #include "xe_sriov_vf_ccs.h"
> @@ -1218,7 +1217,6 @@ static void vf_post_migration_recovery(struct xe_gt *gt)
>   
>   	xe_gt_sriov_dbg(gt, "migration recovery in progress\n");
>   
> -	xe_pm_runtime_get(xe);
>   	retry = vf_post_migration_shutdown(gt);
>   	if (retry)
>   		goto queue;
> @@ -1241,12 +1239,10 @@ static void vf_post_migration_recovery(struct xe_gt *gt)
>   
>   	vf_post_migration_kickstart(gt);
>   
> -	xe_pm_runtime_put(xe);
>   	xe_gt_sriov_notice(gt, "migration recovery ended\n");
>   	return;
>   fail:
>   	vf_post_migration_abort(gt);
> -	xe_pm_runtime_put(xe);
>   	xe_gt_sriov_err(gt, "migration recovery failed (%pe)\n", ERR_PTR(err));
>   	xe_device_declare_wedged(xe);
>   	return;
> @@ -1254,7 +1250,6 @@ static void vf_post_migration_recovery(struct xe_gt *gt)
>   queue:
>   	xe_gt_sriov_info(gt, "Re-queuing migration recovery\n");
>   	queue_work(gt->ordered_wq, &gt->sriov.vf.migration.worker);
> -	xe_pm_runtime_put(xe);
>   }
>   
>   static void migration_worker_func(struct work_struct *w)


  reply	other threads:[~2025-10-22 10:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22  0:55 [PATCH 0/3] Fix low hanging workqueue / reclaim issues Matthew Brost
2025-10-22  0:55 ` [PATCH 1/3] drm/xe: Check return value of GGTT workqueue allocation Matthew Brost
2025-10-22  9:54   ` Matthew Auld
2025-10-22  0:55 ` [PATCH 2/3] drm/xe: Do not wake device during a GT reset Matthew Brost
2025-10-22 10:03   ` Matthew Auld
2025-10-22  0:55 ` [PATCH 3/3] drm/xe: Avoid PM wake reference during VF migration Matthew Brost
2025-10-22 10:08   ` Matthew Auld [this message]
2025-10-22  2:32 ` ✓ CI.KUnit: success for Fix low hanging workqueue / reclaim issues Patchwork
2025-10-22  4:20 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-22  6:24 ` ✓ Xe.CI.Full: " 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=9b2419c8-efd0-41fc-98e4-f4324ac423f4@intel.com \
    --to=matthew.auld@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@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