mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: "Matthew Brost" <matthew.brost@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Matt Roper" <matthew.d.roper@intel.com>,
	"Lucas De Marchi" <demarchi@kernel.org>,
	"Riana Tauro" <riana.tauro@intel.com>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Matthew Auld" <matthew.auld@intel.com>,
	"Shuicheng Lin" <shuicheng.lin@intel.com>,
	"Armin Wolf" <W_Armin@gmx.de>,
	"Zhanjun Dong" <zhanjun.dong@intel.com>,
	"Michal Wajdeczko" <michal.wajdeczko@intel.com>,
	"Piotr Piórkowski" <piotr.piorkowski@intel.com>,
	"Tejas Upadhyay" <tejas.upadhyay@intel.com>,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: xe: select configfs
Date: Wed, 11 Nov 2026 14:01:45 -0500	[thread overview]
Message-ID: <avS7mZMrS7nQv_RK@intel.com> (raw)
In-Reply-To: <20261026102603.2045493-1-arnd@kernel.org>

On Mon, Oct 26, 2026 at 11:25:50AM +0100, Arnd Bergmann wrote:
> From: Arnd Bergmann <arnd@arndb.de>
> 
> The original addition of configfs to xe missed a compile-time dependency,
> which leads to a link failure when configfs is enabled as a loadable module:
> 
> ld.lld-21: error: undefined symbol: xe_configfs_get_survivability_mode
> >>> referenced by xe_survivability_mode.c:224
> >>>               drivers/gpu/drm/xe/xe_survivability_mode.o:(xe_survivability_mode_is_requested) in archive vmlinux.a
> 
> A recent workaround added a 'IS_REACHABLE()' check around the calls into
> configfs, which makes it link in this configuration, but this is generally
> a bad idea because it makes the actual behavior inconsistent and confusing
> to users that expect configfs to work if both xe and configfs are enabled.
> 
> Use 'select CONFIGFS_FS' instead, like every other configfs user does,
> and remove the unnecessary stub functions. There is little practical
> difference here as anyone using XE graphics is likely to have a complex
> configuration that already selects configfs anyway, and the link error
> or the IS_REACHABLE() would only manifest during randconfig testing.
> 
> Fixes: 30499cbd7961 ("drm/xe: Fix build with DRM_XE=y and CONFIGFS_FS=m")
> Fixes: 16280ded45fb ("drm/xe: Add configfs to enable survivability mode")
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
>  drivers/gpu/drm/xe/Kconfig       |  1 +
>  drivers/gpu/drm/xe/xe_configfs.h | 30 ------------------------------
>  2 files changed, 1 insertion(+), 30 deletions(-)
> 
> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
> index 4fc8abdc5cb6..b52a8dc28f97 100644
> --- a/drivers/gpu/drm/xe/Kconfig
> +++ b/drivers/gpu/drm/xe/Kconfig
> @@ -11,6 +11,7 @@ config DRM_XE
>  	# the shmem_readpage() which depends upon tmpfs
>  	select SHMEM
>  	select TMPFS
> +	select CONFIGFS_FS

Perhaps another option would be what Jani had suggested:

config DRM_XE_CONFIGFS
	def_bool y
	depends on DRM_XE && CONFIGFS_FS
	depends on CONFIGFS_FS=y || DRM_XE=m

But anyway, we are depending more and more on the configfs for
production choices. So, let's go with you select and close this
for good.

I'm pushing this to drm-xe-next.

Thanks for the patch.


>  	select DRM_BUDDY
>  	select DRM_CLIENT_SELECTION
>  	select DRM_KMS_HELPER
> diff --git a/drivers/gpu/drm/xe/xe_configfs.h b/drivers/gpu/drm/xe/xe_configfs.h
> index 327b648944ff..d726800de26a 100644
> --- a/drivers/gpu/drm/xe/xe_configfs.h
> +++ b/drivers/gpu/drm/xe/xe_configfs.h
> @@ -14,7 +14,6 @@
>  
>  struct pci_dev;
>  
> -#if IS_REACHABLE(CONFIG_CONFIGFS_FS)
>  int xe_configfs_init(void);
>  void xe_configfs_exit(void);
>  void xe_configfs_check_device(struct pci_dev *pdev);
> @@ -36,34 +35,5 @@ u32 xe_configfs_get_ctx_restore_post_bb(struct pci_dev *pdev,
>  unsigned int xe_configfs_get_max_vfs(struct pci_dev *pdev);
>  bool xe_configfs_admin_only_pf(struct pci_dev *pdev);
>  #endif
> -#else
> -static inline int xe_configfs_init(void) { return 0; }
> -static inline void xe_configfs_exit(void) { }
> -static inline void xe_configfs_check_device(struct pci_dev *pdev) { }
> -static inline bool xe_configfs_get_survivability_mode(struct pci_dev *pdev) { return false; }
> -static inline bool xe_configfs_primary_gt_allowed(struct pci_dev *pdev) { return true; }
> -static inline bool xe_configfs_media_gt_allowed(struct pci_dev *pdev) { return true; }
> -static inline u64 xe_configfs_get_engines_allowed(struct pci_dev *pdev) { return U64_MAX; }
> -static inline bool xe_configfs_get_psmi_enabled(struct pci_dev *pdev) { return false; }
> -static inline bool xe_configfs_get_enable_multi_queue(struct pci_dev *pdev) { return true; }
> -static inline u32 xe_configfs_get_migrate_ulls_period_ms(struct pci_dev *pdev) { return 5; }
> -static inline bool xe_configfs_get_disable_vram_page_offline(struct pci_dev *pdev) { return false; }
> -static inline u32 xe_configfs_get_ctx_restore_mid_bb(struct pci_dev *pdev,
> -						     enum xe_engine_class class,
> -						     const u32 **cs) { return 0; }
> -static inline u32 xe_configfs_get_ctx_restore_post_bb(struct pci_dev *pdev,
> -						      enum xe_engine_class class,
> -						      const u32 **cs) { return 0; }
> -#ifdef CONFIG_PCI_IOV
> -static inline unsigned int xe_configfs_get_max_vfs(struct pci_dev *pdev)
> -{
> -	return xe_modparam.max_vfs;
> -}
> -static inline bool xe_configfs_admin_only_pf(struct pci_dev *pdev)
> -{
> -	return XE_DEFAULT_ADMIN_ONLY_PF;
> -}
> -#endif
> -#endif
>  
>  #endif
> -- 
> 2.53.0
> 

      reply	other threads:[~2026-11-11 19:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 10:25 Arnd Bergmann
2026-11-11 19:01 ` Rodrigo Vivi [this message]

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=avS7mZMrS7nQv_RK@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=W_Armin@gmx.de \
    --cc=airlied@gmail.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=demarchi@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.brost@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=michal.wajdeczko@intel.com \
    --cc=piotr.piorkowski@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=shuicheng.lin@intel.com \
    --cc=simona@ffwll.ch \
    --cc=tejas.upadhyay@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=zhanjun.dong@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

all inboxes | Powered by JetHome®