[MODERATED] Re: [PATCH v7 04/10] TAAv7 4
Borislav Petkov <[email protected]>
| Newsgroups | org.kernel.lore.historical-speck |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Oct 22, 2019 at 06:51:12PM +0200, Borislav Petkov wrote:
> > +{
> > + if (!boot_cpu_has_bug(X86_BUG_TAA))
> > + return 0;
> > +
> > + if (!str)
> > + return -EINVAL;
> > +
> > + if (!strcmp(str, "off")) {
> > + taa_mitigation = TAA_MITIGATION_OFF;
> > + } else if (!strcmp(str, "full")) {
> > + taa_mitigation = TAA_MITIGATION_VERW;
> > + } else if (!strcmp(str, "full,nosmt")) {
> > + taa_mitigation = TAA_MITIGATION_VERW;
> > + taa_nosmt = true;
> > + }
> > +
> > + return 0;
> > +}
> > +early_param("tsx_async_abort", tsx_async_abort_cmdline);
>
> Say what now?!
>
> The previous patch added this:
>
> tsx= [X86] Control Transactional Synchronization
> Extensions (TSX) feature in Intel processors that
> support TSX control.
>
> This parameter controls the TSX feature. The options are:
>
> on - Enable TSX on the system.
> off - Disable TSX on the system.
>
> So what is the final name of command line option now?
Yah, Josh just set me straight: there's two flags. Yuck. I'm willing to
bet I won't be the only one to get confused by this.
tsx=
taa=
is probably marginally better but someone might have a better idea.
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg
--