From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "Roper, Matthew D" <matthew.d.roper@intel.com>,
"Wajdeczko, Michal" <Michal.Wajdeczko@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Tauro, Riana" <riana.tauro@intel.com>,
"Gupta, Anshuman" <anshuman.gupta@intel.com>
Subject: Re: [PATCH] drm/xe: select CONFIGFS_FS dependency
Date: Fri, 19 Dec 2025 17:00:36 +0000 [thread overview]
Message-ID: <2c98afb4a0709d622ca7345b65b75690c73d1c37.camel@intel.com> (raw)
In-Reply-To: <43529e9d-3bd4-44d5-a603-8394a7a0f049@intel.com>
On Fri, 2025-12-19 at 17:42 +0100, Michal Wajdeczko wrote:
>
>
> On 12/19/2025 5:32 PM, Matt Roper wrote:
> > On Fri, Dec 19, 2025 at 11:04:06AM -0500, Rodrigo Vivi wrote:
> > > On Fri, Dec 19, 2025 at 01:35:14PM +0530, Riana Tauro wrote:
> > > > Xe driver uses configfs functions to expose configuration to
> > > > userspace.
> > > > If CONFIGFS_FS is built as module (=m) when Xe is built-in
> > > > (=y),
> > > > undefined reference errors occur.
> > >
> > > Perhaps we don't need this middle phrase. Only the first and the
> > > last.
> > > But anyway, we need the patch in. I just pushed it.
> > >
> > > Thanks,
> > > Rodrigo.
> > >
> > > > Add select CONFIGFS_FS to ensure configfs is built at minimum
> > > > required
> > > > level.
> >
> > If we make this change, shouldn't we also remove all of the #ifdef
> > logic
> > we have to support running without configfs?
well, this could be done in a follow-up patch
>
> but is it a good idea to always back select CONFIGFS ?
that's a great question. We are more and more dependent on configfs
to select options. But we shouldn't be dependent on that to run
with defaults.
Because of both concerns I just removed the patch.
Sorry for having rushed with it.
> maybe the actual fix should be like this:
>
> -xe-$(CONFIG_CONFIGFS_FS) += xe_configfs.o
> +
> +ifdef CONFIG_CONFIGFS_FS
> + xe-y += xe_configfs.o
> +endif
I'm not sure if this is also the best option.
Perhaps we should always include the file and let the ifdefs inside the
code deal with it properly?
>
>
> >
> >
> > Matt
> >
> > > >
> > > > Cc: Matt Roper <matthew.d.roper@intel.com>
> > > > Reported-by: kernel test robot <lkp@intel.com>
> > > > Closes:
> > > > https://lore.kernel.org/oe-kbuild-all/202512190827.IeXYj4qg-lkp@intel.com/
> > > > Closes:
> > > > https://lore.kernel.org/oe-kbuild-all/202512181854.hPyTAXc5-lkp@intel.com/
> > > > Closes:
> > > > https://lore.kernel.org/oe-kbuild-all/202512190407.CcUFXX2F-lkp@intel.com/
> > > > Fixes: 16280ded45fb ("drm/xe: Add configfs to enable
> > > > survivability mode")
> > > > Signed-off-by: Riana Tauro <riana.tauro@intel.com>
> > > > ---
> > > > drivers/gpu/drm/xe/Kconfig | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > >
> > > > diff --git a/drivers/gpu/drm/xe/Kconfig
> > > > b/drivers/gpu/drm/xe/Kconfig
> > > > index 4b288eb3f5b0..1094c5fc5bdf 100644
> > > > --- a/drivers/gpu/drm/xe/Kconfig
> > > > +++ b/drivers/gpu/drm/xe/Kconfig
> > > > @@ -46,6 +46,7 @@ config DRM_XE
> > > > select WANT_DEV_COREDUMP
> > > > select AUXILIARY_BUS
> > > > select REGMAP if I2C
> > > > + select CONFIGFS_FS
> > > > help
> > > > Driver for Intel Xe2 series GPUs and later.
> > > > Experimental support
> > > > for Xe series is also available.
> > > > --
> > > > 2.47.1
> > > >
> >
next prev parent reply other threads:[~2025-12-19 17:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-19 8:05 [PATCH] drm/xe: select CONFIGFS_FS dependency Riana Tauro
2025-12-19 8:26 ` ✓ CI.KUnit: success for " Patchwork
2025-12-19 9:00 ` ✓ Xe.CI.BAT: " Patchwork
2025-12-19 16:04 ` [PATCH] " Rodrigo Vivi
2025-12-19 16:32 ` Matt Roper
2025-12-19 16:42 ` Michal Wajdeczko
2025-12-19 16:53 ` Matt Roper
2025-12-19 17:00 ` Vivi, Rodrigo [this message]
2025-12-21 10:48 ` Riana Tauro
2025-12-22 15:10 ` Rodrigo Vivi
2025-12-22 12:42 ` Jani Nikula
2026-01-02 14:57 ` Riana Tauro
2026-01-02 15:13 ` Jani Nikula
2025-12-20 10:07 ` ✗ Xe.CI.Full: failure for " 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=2c98afb4a0709d622ca7345b65b75690c73d1c37.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=Michal.Wajdeczko@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=riana.tauro@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