linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	X86 ML <x86@kernel.org>, Tony Luck <tony.luck@intel.com>
Subject: Re: linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o)
Date: Thu, 19 May 2022 00:29:39 +0200	[thread overview]
Message-ID: <YoVzUxSwhoim9TOX@zn.tnic> (raw)
In-Reply-To: <df5ed1d0-6304-89b8-ad68-0cf6a59d8614@infradead.org>

On Wed, May 18, 2022 at 02:54:45PM -0700, Randy Dunlap wrote:
> 
> 
> On 5/18/22 14:34, Borislav Petkov wrote:
> > On Wed, May 18, 2022 at 02:05:28PM -0700, Randy Dunlap wrote:
> >> on x86_64:
> >>
> >> CONFIG_PROCESSOR_SELECT=y
> >> # CONFIG_CPU_SUP_INTEL is not set   <<<<<
> >> CONFIG_CPU_SUP_AMD=y
> >> # CONFIG_CPU_SUP_HYGON is not set
> >> CONFIG_CPU_SUP_CENTAUR=y
> >> CONFIG_CPU_SUP_ZHAOXIN=y
> >>
> >> CONFIG_MICROCODE=y
> >> CONFIG_MICROCODE_INTEL=y   <<<<<
> >> CONFIG_MICROCODE_AMD=y
> > 
> > Hmm:
> > 
> > $ grep -E "(PROCESSOR_SELECT|CPU_SUP|MICROCODE)" .config
> > CONFIG_PROCESSOR_SELECT=y
> > # CONFIG_CPU_SUP_INTEL is not set
> > CONFIG_CPU_SUP_AMD=y
> > # CONFIG_CPU_SUP_HYGON is not set
> > CONFIG_CPU_SUP_CENTAUR=y
> > CONFIG_CPU_SUP_ZHAOXIN=y
> > CONFIG_MICROCODE=y
> > CONFIG_MICROCODE_INTEL=y
> > CONFIG_MICROCODE_AMD=y
> > CONFIG_MICROCODE_OLD_INTERFACE=y
> > 
> > that builds fine here on tip/master. Or is it linux-next specific? I'd
> > hope not.
> > 
> > Can you send me your whole .config pls and how exactly you reproduce it,
> > i.e., on which tree?
> 
> This is linux-next-20220518. config file is attached.

Ah, got it, that's the IFS thing which uses microcode loader functions.

I think this below but will do more poking tomorrow on a fresh head.

Thx.

---
diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 60e9be91250e..ba1e509d11bb 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1321,7 +1321,6 @@ config X86_REBOOTFIXUPS
 config MICROCODE
 	bool "CPU microcode loading support"
 	default y
-	depends on CPU_SUP_AMD || CPU_SUP_INTEL
 	help
 	  If you say Y here, you will be able to update the microcode on
 	  Intel and AMD processors. The Intel support is for the IA32 family,
@@ -1341,7 +1340,7 @@ config MICROCODE
 
 config MICROCODE_INTEL
 	bool "Intel microcode loading support"
-	depends on MICROCODE
+	depends on CPU_SUP_INTEL && MICROCODE
 	default MICROCODE
 	help
 	  This options enables microcode patch loading support for Intel
@@ -1353,7 +1352,7 @@ config MICROCODE_INTEL
 
 config MICROCODE_AMD
 	bool "AMD microcode loading support"
-	depends on MICROCODE
+	depends on CPU_SUP_AMD && MICROCODE
 	help
 	  If you select this option, microcode patch loading support for AMD
 	  processors will be enabled.
diff --git a/drivers/platform/x86/intel/ifs/Kconfig b/drivers/platform/x86/intel/ifs/Kconfig
index d84491cfb0db..aaaa5503951d 100644
--- a/drivers/platform/x86/intel/ifs/Kconfig
+++ b/drivers/platform/x86/intel/ifs/Kconfig
@@ -1,6 +1,6 @@
 config INTEL_IFS
 	tristate "Intel In Field Scan"
-	depends on X86 && 64BIT && SMP
+	depends on CPU_SUP_INTEL && 64BIT && SMP
 	select INTEL_IFS_DEVICE
 	help
 	  Enable support for the In Field Scan capability in select


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2022-05-18 22:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-18 10:29 linux-next: Tree for May 18 Stephen Rothwell
2022-05-18 21:05 ` linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o) Randy Dunlap
2022-05-18 21:34   ` Borislav Petkov
2022-05-18 21:54     ` Randy Dunlap
2022-05-18 22:29       ` Borislav Petkov [this message]
2022-05-18 22:40         ` Randy Dunlap
2022-05-19 14:55           ` Borislav Petkov
2022-05-19 14:57             ` [PATCH] platform/x86/intel/ifs: Add CPU_SUP_INTEL dependency Borislav Petkov
2022-05-19 17:47               ` Hans de Goede
2022-05-19 15:03             ` [PATCH] x86/microcode: Add explicit CPU vendor dependency Borislav Petkov

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=YoVzUxSwhoim9TOX@zn.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=sfr@canb.auug.org.au \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).