Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Tomasz Lis <tomasz.lis@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: "Michał Winiarski" <michal.winiarski@intel.com>,
	"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Satyanarayana K V P" <satyanarayana.k.v.p@intel.com>
Subject: Re: [PATCH v5 2/5] drm/xe/vf: Revert logic of vf.migration.enabled
Date: Tue, 21 Oct 2025 16:32:59 +0200	[thread overview]
Message-ID: <be926abd-1db8-4bac-829e-673cefe89fd1@intel.com> (raw)
In-Reply-To: <20251021123943.1436375-3-tomasz.lis@intel.com>



On 10/21/2025 2:39 PM, Tomasz Lis wrote:
> Convert `enabled` property into `disabled`.
> 
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Signed-off-by: Tomasz Lis <tomasz.lis@intel.com>
> Suggested-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
>  drivers/gpu/drm/xe/xe_sriov_vf.c       | 6 +++---
>  drivers/gpu/drm/xe/xe_sriov_vf_types.h | 6 +++---
>  2 files changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf.c b/drivers/gpu/drm/xe/xe_sriov_vf.c
> index 911d5720917b..5ad39e315cb5 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_vf.c
> +++ b/drivers/gpu/drm/xe/xe_sriov_vf.c
> @@ -130,7 +130,7 @@
>  bool xe_sriov_vf_migration_supported(struct xe_device *xe)
>  {
>  	xe_assert(xe, IS_SRIOV_VF(xe));
> -	return xe->sriov.vf.migration.enabled;
> +	return !xe->sriov.vf.migration.disabled;
>  }
>  
>  static void vf_disable_migration(struct xe_device *xe, const char *fmt, ...)
> @@ -146,7 +146,7 @@ static void vf_disable_migration(struct xe_device *xe, const char *fmt, ...)
>  	xe_sriov_notice(xe, "migration disabled: %pV\n", &vaf);
>  	va_end(va_args);
>  
> -	xe->sriov.vf.migration.enabled = false;
> +	xe->sriov.vf.migration.disabled = true;
>  }
>  
>  static void vf_migration_init_early(struct xe_device *xe)
> @@ -173,7 +173,7 @@ static void vf_migration_init_early(struct xe_device *xe)
>  						    guc_version.major, guc_version.minor);
>  	}
>  
> -	xe->sriov.vf.migration.enabled = true;
> +	xe->sriov.vf.migration.disabled = false;

this should be just removed (it's false by default)
>  	xe_sriov_dbg(xe, "migration support enabled\n");

and we already agreed that we will just log the "disabled" case
so this line should go away too

>  }
>  
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf_types.h b/drivers/gpu/drm/xe/xe_sriov_vf_types.h
> index 6a0fd0f5463e..d5f72d667817 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_vf_types.h
> +++ b/drivers/gpu/drm/xe/xe_sriov_vf_types.h
> @@ -34,10 +34,10 @@ struct xe_device_vf {
>  	/** @migration: VF Migration state data */
>  	struct {
>  		/**
> -		 * @migration.enabled: flag indicating if migration support
> -		 * was enabled or not due to missing prerequisites
> +		 * @migration.disabled: flag indicating if migration support
> +		 * was turned off due to missing prerequisites
>  		 */
> -		bool enabled;
> +		bool disabled;
>  	} migration;
>  
>  	/** @ccs: VF CCS state data */


  reply	other threads:[~2025-10-21 14:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 12:39 [PATCH v5 0/5] drm/xe/vf: Minor fixes to post-migration recovery Tomasz Lis
2025-10-21 12:39 ` [PATCH v5 1/5] drm/xe/vf: Helper for telling whether CCS migration BBs are needed Tomasz Lis
2025-10-21 14:29   ` Michal Wajdeczko
2025-10-21 12:39 ` [PATCH v5 2/5] drm/xe/vf: Revert logic of vf.migration.enabled Tomasz Lis
2025-10-21 14:32   ` Michal Wajdeczko [this message]
2025-10-21 12:39 ` [PATCH v5 3/5] drm/xe/vf: Fix GuC FW check for VF migration support Tomasz Lis
2025-10-21 14:42   ` Michal Wajdeczko
2025-10-21 12:39 ` [PATCH v5 4/5] drm/xe: Assert that VF will never use fixed placement of BOs Tomasz Lis
2025-10-21 12:39 ` [PATCH v5 5/5] drm/xe/vf: Do not disable VF migration on ATS-M Tomasz Lis
2025-10-21 13:56 ` ✓ CI.KUnit: success for drm/xe/vf: Minor fixes to post-migration recovery (rev5) Patchwork
2025-10-21 15:03 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-21 16:33 ` ✗ 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=be926abd-1db8-4bac-829e-673cefe89fd1@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=piotr.piorkowski@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