From: Harry Austen <hpausten@protonmail.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: "Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Jani Nikula" <jani.nikula@intel.com>
Subject: Re: [PATCH v4] drm/xe: Allow building as kernel built-in
Date: Wed, 21 May 2025 20:51:24 +0000 [thread overview]
Message-ID: <DA24WEEONQS4.2KGRJLM9YNTG3@protonmail.com> (raw)
In-Reply-To: <s43s6p2p6frhqg64r42s5owhyiczkfrsgmt5fecosmout73x5m@aq22nie755nt>
On Wed May 21, 2025 at 4:11 PM BST, Lucas De Marchi wrote:
> On Wed, May 21, 2025 at 08:35:05AM +0000, Harry Austen wrote:
> >On Mon May 19, 2025 at 4:14 PM BST, Maarten Lankhorst wrote:
> >> Hey,
> >>
> >> On 2025-05-16 12:42, Harry Austen wrote:
> >>> Fix Kconfig symbol dependency on KUNIT, which isn't actually required
> >>> for XE to be built-in. However, if KUNIT is enabled, it must be built-in
> >>> too.
> >>>
> >>> Also, allow DRM_XE_DISPLAY to be built-in. But only as long as DRM_I915
> >>> isn't, since that results in duplicate symbol errors.
> >>>
> >>> Fixes: 08987a8b6820 ("drm/xe: Fix build with KUNIT=m")
> >>> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> >>> Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> >>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
> >>> Signed-off-by: Harry Austen <hpausten@protonmail.com>
> >>> Acked-by: Jani Nikula <jani.nikula@intel.com>
> >>> ---
> >>> v4: Add Jani Nikula's Acked-by tag
> >>> v3: Simplify KUNIT dependency, as suggested by Jani Nikula
> >>> v2: Ensure DRM_XE_DISPLAY and DRM_I915 can't both be built-in
> >>>
> >>> drivers/gpu/drm/xe/Kconfig | 5 +++--
> >>> 1 file changed, 3 insertions(+), 2 deletions(-)
> >>>
> >>> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
> >>> index 9bce047901b22..214f40264fa12 100644
> >>> --- a/drivers/gpu/drm/xe/Kconfig
> >>> +++ b/drivers/gpu/drm/xe/Kconfig
> >>> @@ -1,7 +1,8 @@
> >>> # SPDX-License-Identifier: GPL-2.0-only
> >>> config DRM_XE
> >>> tristate "Intel Xe Graphics"
> >>> - depends on DRM && PCI && MMU && (m || (y && KUNIT=y))
> >>> + depends on DRM && PCI && MMU
> >>> + depends on KUNIT || KUNIT=n
> >>> select INTERVAL_TREE
> >>> # we need shmfs for the swappable backing store, and in particular
> >>> # the shmem_readpage() which depends upon tmpfs
> >>> @@ -51,7 +52,7 @@ config DRM_XE
> >>>
> >>> config DRM_XE_DISPLAY
> >>> bool "Enable display support"
> >>> - depends on DRM_XE && DRM_XE=m && HAS_IOPORT
> >>> + depends on DRM_XE && (DRM_XE=m || DRM_I915!=y) && HAS_IOPORT
> >>> select FB_IOMEM_HELPERS if DRM_FBDEV_EMULATION
> >>> select I2C
> >>> select I2C_ALGOBIT
> >> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> >
> >Thanks!
> >
> >>
> >> Can we also get rid of the IOSF_MBI select? Not even xe_display depends on it, leftover from initial porting. :)
> >
> >As this seems unrelated, I'd be happy to submit a separate patch for this
> >afterwards. Thanks for the suggestion.
>
> same comment as in the previous version of this patch. What I don't like
> is that it doesn't prevent you to do a bad selection. Instead if you set
> DRM_XE=y and DRM_I915=y, you lose DRM_XE_DISPLAY. Silently. This is
> equivalent of chosing the options via make menuconfig:
>
> # initial state
> ./scripts/config --state CONFIG_DRM_XE --state CONFIG_DRM_XE_DISPLAY --state CONFIG_DRM_I915
> m
> y
> m
>
> # set CONFIG_DRM_XE to built-in
> ./scripts/config -e CONFIG_DRM_XE && make -s olddefconfig
> ./scripts/config --state CONFIG_DRM_XE --state CONFIG_DRM_XE_DISPLAY --state CONFIG_DRM_I915
> y
> y
> m
>
> # set CONFIG_DRM_I915 to built-in, we lose display with xe
> $ ~/p/linux-dim/drm-xe-next/scripts/config --state CONFIG_DRM_XE --state CONFIG_DRM_XE_DISPLAY --state CONFIG_DRM_I915
> y
> undef
> y
>
> I'm not sure how to prevent setting CONFIG_DRM_I915=y if
> CONFIG_DRM_XE_DISPLAY is selected.
Ah interesting, thanks for the example. I'll try a few different things and see
if I can get more sensible behaviour.
>
> Lucas De Marchi
>
> >
> >Harry
> >
next prev parent reply other threads:[~2025-05-21 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 10:42 Harry Austen
2025-05-19 15:14 ` Maarten Lankhorst
2025-05-21 8:35 ` Harry Austen
2025-05-21 15:11 ` Lucas De Marchi
2025-05-21 20:51 ` Harry Austen [this message]
2025-06-26 20:51 ` Lucas De Marchi
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=DA24WEEONQS4.2KGRJLM9YNTG3@protonmail.com \
--to=hpausten@protonmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=thomas.hellstrom@linux.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®