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 v6 1/4] drm/xe/vf: Revert logic of vf.migration.enabled
Date: Tue, 21 Oct 2025 20:13:46 +0200 [thread overview]
Message-ID: <f95b87cf-4782-442b-8ab1-3c73354e67fe@intel.com> (raw)
In-Reply-To: <20251021181250.1541639-2-tomasz.lis@intel.com>
On 10/21/2025 8:12 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>
Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> v2: removed writing false to what is already zeroed out (Michal)
>
> drivers/gpu/drm/xe/xe_sriov_vf.c | 7 ++-----
> drivers/gpu/drm/xe/xe_sriov_vf_types.h | 6 +++---
> 2 files changed, 5 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf.c b/drivers/gpu/drm/xe/xe_sriov_vf.c
> index 911d5720917b..0d8135f3927c 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)
> @@ -172,9 +172,6 @@ static void vf_migration_init_early(struct xe_device *xe)
> "CCS migration requires GuC ABI >= 1.23 but only %u.%u found",
> guc_version.major, guc_version.minor);
> }
> -
> - xe->sriov.vf.migration.enabled = true;
> - xe_sriov_dbg(xe, "migration support enabled\n");
> }
>
> /**
> 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 */
next prev parent reply other threads:[~2025-10-21 18:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 18:12 [PATCH v6 0/4] drm/xe/vf: Minor fixes to post-migration recovery Tomasz Lis
2025-10-21 18:12 ` [PATCH v6 1/4] drm/xe/vf: Revert logic of vf.migration.enabled Tomasz Lis
2025-10-21 18:13 ` Michal Wajdeczko [this message]
2025-10-21 18:12 ` [PATCH v6 2/4] drm/xe/vf: Fix GuC FW check for VF migration support Tomasz Lis
2025-10-21 18:39 ` Michal Wajdeczko
2025-10-21 22:39 ` Lis, Tomasz
2025-10-21 18:12 ` [PATCH v6 3/4] drm/xe: Assert that VF will never use fixed placement of BOs Tomasz Lis
2025-10-21 18:12 ` [PATCH v6 4/4] drm/xe/vf: Do not disable VF migration on ATS-M Tomasz Lis
2025-10-21 18:18 ` ✓ CI.KUnit: success for drm/xe/vf: Minor fixes to post-migration recovery (rev6) 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=f95b87cf-4782-442b-8ab1-3c73354e67fe@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