lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY5PR11MB636685688893B7873C3BE85AED91A@CY5PR11MB6366.namprd11.prod.outlook.com>
Date: Wed, 28 Jan 2026 06:57:05 +0000
From: "Usyskin, Alexander" <alexander.usyskin@...el.com>
To: Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven
	<geert+renesas@...der.be>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Simon Richter <Simon.Richter@...yros.de>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE

> Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
> 
> On Wed, Jan 28, 2026, at 07:41, Usyskin, Alexander wrote:
> >> Subject: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
> >>
> >> The Intel Management Engine Interface is only present on x86 platforms
> >> and Intel Xe graphics cards.  Hence add a dependency on X86 or DRM_XE,
> >> to prevent asking the user about this driver when configuring a kernel
> >> for a non-x86 architecture and without Xe graphics support.
> >>
> >> Fixes: 25f9b0d351552f63 ("misc/mei: Allow building Intel ME interface on
> >> non-x86")
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@...der.be>
> >> ---
> >>  drivers/misc/mei/Kconfig | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
> >> index 5902dd1ee44baf16..094fb1dde0fe80c5 100644
> >> --- a/drivers/misc/mei/Kconfig
> >> +++ b/drivers/misc/mei/Kconfig
> >> @@ -3,6 +3,7 @@
> >>  config INTEL_MEI
> >>  	tristate "Intel Management Engine Interface"
> >>  	depends on PCI
> >> +	depends on X86 || DRM_XE!=n || COMPILE_TEST
> >
> > Add DRM_I915 here too, MEI may depend on it.
> 
> Based on the patch description, shouldn't the dependency allow
> compile-testing only if both XE and I915 are turned off, as in
> 
>       depends on X86  || (DRM_XE=n && DRM_I915=n && COMPILE_TEST)
> 
> ?
> 
> As far as I can tell, i915 and xe will attempt (and fail) to
> use MEI if that is enabled, so there is no point in enabling
> INTEL_MEI outside of compile-testing even if XE is built.
> 

There are different usages of mei:
- for discrete graphics xe/i915 will load mei via auxiliary device also on non x86.
- for integrated xe/i915 communicate with mei for on-chip CSME - this scenario is x86 only.

IMO this should cover all:
depends on X86 || DRM_XE!=n || DRM_I915!=n || COMPILE_TEST

- - 
Thanks,
Sasha


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ