linux-kernel - Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM

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: <CAMuHMdVEdps0_H-Yr0aO+MDxZjXWjoCAY-bZyr04HYVdYQCwSw@mail.gmail.com>
Date: Thu, 29 Jan 2026 09:17:30 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Simon Richter <Simon.Richter@...yros.de>
Cc: "Usyskin, Alexander" <alexander.usyskin@...el.com>, Arnd Bergmann <arnd@...db.de>, 
	Geert Uytterhoeven <geert+renesas@...der.be>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE

Hi Simon,

On Thu, 29 Jan 2026 at 05:45, Simon Richter <Simon.Richter@...yros.de> wrote:
> On 1/28/26 3:57 PM, Usyskin, Alexander wrote:
> > 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
>
> Is there discrete i915?
>
> DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant, which
> is why I didn't add it in my version of the patch. If DRM_I915 is useful
> on non-x86 we might want to change that as well.

Then the dependency of DRM_I915 on X86 should be dropped first...

> Also, is there any policy on dependency ordering? On non-X86, INTEL_MEI
> becomes available only after selecting DRM_XE, which is in a directory
> included much later, so the question is not shown initially, is that a
> problem?

Let's give it a try on arm64.
Remove "# CONFIG_DRM_XE is not set" from .config.

    $ make oldconfig
    [...]
      Intel Xe2 Graphics (DRM_XE) [N/y/?] (NEW) y
    [...]
    Intel Management Engine Interface (INTEL_MEI) [N/y/?] (NEW) y
      ME Enabled Intel Chipsets (INTEL_MEI_ME) [Y/n/?] (NEW)
    [...]

So the ordering is not an issue.

I only wonder about some of the other INTEL_MEI_* options.
I think e.g. INTEL_MEI_ME now needs a dependency on X86, as I doubt
any of these Intel Chipsets are used on non-x86?

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds