mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
	x86-ml <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Luis Chamberlain <mcgrof@kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] x86/microcode: Do not select FW_LOADER
Date: Wed, 10 Jun 2020 10:16:09 +0200	[thread overview]
Message-ID: <20200610081609.GA14118@zn.tnic> (raw)
In-Reply-To: <20200610042911.GA20058@gondor.apana.org.au>

On Wed, Jun 10, 2020 at 02:29:11PM +1000, Herbert Xu wrote:
> The x86 microcode support works just fine without FW_LOADER.  In
> fact these days most people load them early in boot so FW_LOADER
> never gets into the picture anyway.

What's the use case here?

$ git grep -E "select.*FW_LOADER" | wc -l
132

so this thing gets selected anyway, practically.

Also, I'm working on removing that homegrown get_builtin_firmware() and
use the one in the fw loader:

https://lkml.kernel.org/r/20200408094526.GC24663@zn.tnic

Leaving in the rest for reference.

> People who need the FW_LOADER capability can still enable it.
> 
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
> 
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 1d6104ea8af0..8aac7a65bfbb 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1296,7 +1296,6 @@ config MICROCODE
>  	bool "CPU microcode loading support"
>  	default y
>  	depends on CPU_SUP_AMD || CPU_SUP_INTEL
> -	select FW_LOADER
>  	---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,
> @@ -1318,7 +1317,6 @@ config MICROCODE_INTEL
>  	bool "Intel microcode loading support"
>  	depends on MICROCODE
>  	default MICROCODE
> -	select FW_LOADER
>  	---help---
>  	  This options enables microcode patch loading support for Intel
>  	  processors.
> @@ -1330,7 +1328,6 @@ config MICROCODE_INTEL
>  config MICROCODE_AMD
>  	bool "AMD microcode loading support"
>  	depends on MICROCODE
> -	select FW_LOADER
>  	---help---
>  	  If you select this option, microcode patch loading support for AMD
>  	  processors will be enabled.
> diff --git a/arch/x86/kernel/cpu/microcode/core.c b/arch/x86/kernel/cpu/microcode/core.c
> index 7019d4b2df0c..5524ea15b3df 100644
> --- a/arch/x86/kernel/cpu/microcode/core.c
> +++ b/arch/x86/kernel/cpu/microcode/core.c
> @@ -145,7 +145,6 @@ extern struct builtin_fw __end_builtin_fw[];
>  
>  bool get_builtin_firmware(struct cpio_data *cd, const char *name)
>  {
> -#ifdef CONFIG_FW_LOADER
>  	struct builtin_fw *b_fw;
>  
>  	for (b_fw = __start_builtin_fw; b_fw != __end_builtin_fw; b_fw++) {
> @@ -155,7 +154,6 @@ bool get_builtin_firmware(struct cpio_data *cd, const char *name)
>  			return true;
>  		}
>  	}
> -#endif
>  	return false;
>  }
>  
> -- 
> Email: Herbert Xu <herbert@gondor.apana.org.au>
> Home Page: http://gondor.apana.org.au/~herbert/
> PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

-- 
Regards/Gruss,
    Boris.

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

  reply	other threads:[~2020-06-10  8:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10  4:29 Herbert Xu
2020-06-10  8:16 ` Borislav Petkov [this message]
2020-06-10 10:28   ` Herbert Xu
2020-06-10 10:34     ` Borislav Petkov
2020-06-10 10:41       ` Herbert Xu
2020-06-10 10:48         ` Borislav Petkov
2020-06-10 11:05           ` [v2 PATCH] " Herbert Xu
2020-06-10 13:12   ` [PATCH] " Luis Chamberlain
2020-06-10 13:46     ` Borislav Petkov
2020-06-10 14:01       ` Luis Chamberlain
2020-06-15 10:03 ` [tip: x86/microcode] " tip-bot2 for Herbert Xu

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=20200610081609.GA14118@zn.tnic \
    --to=bp@alien8.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®