[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v4 4/4] x86/ucode: Utilize ucode_force and remove opt_ucode_allow_same
On 28.05.2024 17:29, Fouad Hilly wrote: > --- a/docs/misc/xen-command-line.pandoc > +++ b/docs/misc/xen-command-line.pandoc > @@ -2648,7 +2648,7 @@ performance. > Alternatively, selecting `tsx=1` will re-enable TSX at the users own risk. > > ### ucode > -> `= List of [ <integer> | scan=<bool>, nmi=<bool>, allow-same=<bool> ]` > +> `= List of [ <integer> | scan=<bool>, nmi=<bool> ]` > > Applicability: x86 > Default: `nmi` > @@ -2680,11 +2680,6 @@ precedence over `scan`. > stop_machine context. In NMI handler, even NMIs are blocked, which is > considered safer. The default value is `true`. > > -'allow-same' alters the default acceptance policy for new microcode to permit > -trying to reload the same version. Many CPUs will actually reload microcode > -of the same version, and this allows for easy testing of the late microcode > -loading path. > - > ### unrestricted_guest (Intel) > > `= <boolean>` Removal of a command line (sub-)option nowadays wants accompanying by a CHANGELOG.md entry. Jan
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |