Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	intel-xe@lists.freedesktop.org,
	"Matthew Brost" <matthew.brost@intel.com>,
	"Tomasz Lis" <tomasz.lis@intel.com>
Cc: <dri-devel@lists.freedesktop.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Lukasz Laguna <lukasz.laguna@intel.com>
Subject: Re: [PATCH] drm/xe/vf: Enable VF resource fixup unconditionally
Date: Fri, 7 Nov 2025 17:41:27 +0100	[thread overview]
Message-ID: <515fb46c-0711-4afc-89ea-31fc076f3396@intel.com> (raw)
In-Reply-To: <20251107161000.1938186-1-michal.winiarski@intel.com>



On 11/7/2025 5:10 PM, Michał Winiarski wrote:
> All the feature enabling code is in place - drop the debug flag
> requirement for VF resource fixup.
> 
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>

Reviewed-by: Michal Wajdeczko <michal.wajdeczko@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_sriov_vf.c | 8 --------
>  1 file changed, 8 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_sriov_vf.c b/drivers/gpu/drm/xe/xe_sriov_vf.c
> index 39c829daa97c7..284ce37ca92d7 100644
> --- a/drivers/gpu/drm/xe/xe_sriov_vf.c
> +++ b/drivers/gpu/drm/xe/xe_sriov_vf.c
> @@ -156,14 +156,6 @@ void xe_sriov_vf_migration_disable(struct xe_device *xe, const char *fmt, ...)
>  
>  static void vf_migration_init_early(struct xe_device *xe)
>  {
> -	/*
> -	 * TODO: Add conditions to allow specific platforms, when they're
> -	 * supported at production quality.
> -	 */
> -	if (!IS_ENABLED(CONFIG_DRM_XE_DEBUG))
> -		return xe_sriov_vf_migration_disable(xe,
> -				"experimental feature not available on production builds");
> -
>  	if (!xe_device_has_memirq(xe))
>  		return xe_sriov_vf_migration_disable(xe, "requires memory-based IRQ support");
>  


  parent reply	other threads:[~2025-11-07 16:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-07 16:10 [PATCH] drm/xe/vf: Enable VF resource fixup unconditionally Michał Winiarski
2025-11-07 16:17 ` ✓ CI.KUnit: success for " Patchwork
2025-11-07 16:41 ` Michal Wajdeczko [this message]
2025-11-07 17:07 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-09  1:58 ` ✗ 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=515fb46c-0711-4afc-89ea-31fc076f3396@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=lukasz.laguna@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=michal.winiarski@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.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