All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Vallejo <alejandro.garciavallejo@amd.com>
To: Jan Beulich <jbeulich@suse.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>
Cc: "Doug Goldstein" <cardoe@cardoe.com>,
	"Stefano Stabellini" <sstabellini@kernel.org>,
	"Anthony PERARD" <anthony.perard@vates.tech>,
	"Michal Orzel" <michal.orzel@amd.com>,
	"Julien Grall" <julien@xen.org>,
	"Roger Pau Monné" <roger.pau@citrix.com>,
	"Daniel P. Smith" <dpsmith@apertussolutions.com>,
	"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 2/2] x86/ucode: Add Kconfig option to remove microcode loading
Date: Tue, 13 Jan 2026 11:45:13 +0100	[thread overview]
Message-ID: <DFNEFH1XI008.1RFBCEC15UHXU@amd.com> (raw)
In-Reply-To: <5b00ab27-5ad8-46c0-92fa-a1fa4b65bd99@suse.com>

On Tue Jan 13, 2026 at 9:58 AM CET, Jan Beulich wrote:
> On 12.01.2026 18:15, Andrew Cooper wrote:
>> On 12/01/2026 3:02 pm, Alejandro Vallejo wrote:
>>> --- a/xen/arch/x86/Kconfig
>>> +++ b/xen/arch/x86/Kconfig
>>> @@ -331,8 +331,20 @@ config REQUIRE_NX
>>>  	  was unavailable. However, if enabled, Xen will no longer boot on
>>>  	  any CPU which is lacking NX support.
>>>  
>>> -config UCODE_SCAN_DEFAULT
>>> +config MICROCODE_LOADING
>>> +	bool "Microcode loading"
>>> +	default y
>>> +	help
>>> +	  Support updating the microcode revision of available CPUs with a newer
>>> +	  vendor-provided microcode blob. Microcode updates address some classes of
>>> +	  silicon defects. It's a very common delivery mechanism for fixes or
>>> +	  workarounds for speculative execution vulnerabilities.
>>> +
>>> +	  If unsure, say Y.
>> 
>> Please don't re-iterate the default.  It's a waste.
>
> Well, first of all we should be consistent: Either we always have such a brief
> sentence in the help texts of boolean options, or we never have. Who knows -
> cleaning this up thoughout the tree may even address some anomalies (where the
> sentence and the default setting disagree).
>
> Jan

Is that a request to add missing ones while fixing existing mismatches or remove
them? Not as part of this series in any case, but do you have agreement on the
course of action?

Cheers,
Alejandro


  reply	other threads:[~2026-01-13 10:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 15:02 [PATCH v2 0/2] Add Kconfig option to remove microcode loading support Alejandro Vallejo
2026-01-12 15:02 ` [PATCH v2 1/2] x86/ucode: Fix typo s/mitigiated/mitigated/ Alejandro Vallejo
2026-01-12 15:44   ` Andrew Cooper
2026-01-12 15:02 ` [PATCH v2 2/2] x86/ucode: Add Kconfig option to remove microcode loading Alejandro Vallejo
2026-01-12 17:15   ` Andrew Cooper
2026-01-12 18:47     ` Alejandro Vallejo
2026-01-12 19:12       ` Alejandro Vallejo
2026-01-12 19:51         ` Andrew Cooper
2026-01-12 19:47       ` Andrew Cooper
2026-01-13 10:43         ` Alejandro Vallejo
2026-01-13  8:58     ` Jan Beulich
2026-01-13 10:45       ` Alejandro Vallejo [this message]
2026-01-13 10:49         ` Jan Beulich

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=DFNEFH1XI008.1RFBCEC15UHXU@amd.com \
    --to=alejandro.garciavallejo@amd.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@vates.tech \
    --cc=cardoe@cardoe.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=jbeulich@suse.com \
    --cc=julien@xen.org \
    --cc=marmarek@invisiblethingslab.com \
    --cc=michal.orzel@amd.com \
    --cc=roger.pau@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.