From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bp@suse.de>
Received: from mail.linutronix.de (193.142.43.55:993) by
  crypto-ml.lab.linutronix.de with IMAP4-SSL for <speck@linutronix.de>; 22 Oct
  2019 19:28:37 -0000
Received: from mx2.suse.de ([195.135.220.15] helo=mx1.suse.de)
	by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
	(Exim 4.80)
	(envelope-from <bp@suse.de>)
	id 1iMzpc-0005f3-Ca
	for speck@linutronix.de; Tue, 22 Oct 2019 21:28:36 +0200
Received: from relay2.suse.de (unknown [195.135.220.254])
	by mx1.suse.de (Postfix) with ESMTP id 992BFB2D4
	for <speck@linutronix.de>; Tue, 22 Oct 2019 19:28:28 +0000 (UTC)
Date: Tue, 22 Oct 2019 21:28:20 +0200
From: Borislav Petkov <bp@suse.de>
Subject: [MODERATED] Re: [PATCH v7 04/10] TAAv7 4
Message-ID: <20191022192820.GU31458@zn.tnic>
References: <cover.1571688957.git.pawan.kumar.gupta@linux.intel.com>
 <20191022165112.GK31458@zn.tnic>
 <20191022170230.GM31458@zn.tnic>
 <20191022180032.GF29216@guptapadev.amr>
 <20191022181215.GP31458@zn.tnic>
 <20191022191614.GA26396@agluck-desk2.amr.corp.intel.com>
MIME-Version: 1.0
In-Reply-To: <20191022191614.GA26396@agluck-desk2.amr.corp.intel.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
To: speck@linutronix.de
List-ID: <speck.linutronix.de>

On Tue, Oct 22, 2019 at 12:16:14PM -0700, speck for Luck, Tony wrote:
> It might have been Linus that objected to "taa" (but I can't
> recall if it was for the sysfs file name, or the boot argument)
>=20
> Rationale was that in a couple of years time nobody will
> remember what "taa" stands for.

Oh, I know that. That's why we have spec_store_bypass_disable
and not ssbd. Well, we had ssbd and actually, we should have
spec_store_bypass=3D(disable|enable|...) if we have to be strict but I
digress...

My point is that it would be helpful if those things were called
differently.

Or, a completely different idea: I wonder if we could merge the two
options like we do for l1tf=3D for example where we have

	l1tf=3D<opt1>,<opt2>

and then do:

	tsx=3Don,async_abort_full
	tsx=3Don,async_abort_full,nosmt
	tsx=3Doff

That should even diminish the number of combinations because once you've
supplied "tsx=3Doff" for example, async_abort doesn't matter.

So you only get to deal with the "=3Don" case and all the possibilities
coming with it.

It sure will simplify the code even further, methinks.

--=20
Regards/Gruss,
    Boris.

SUSE Software Solutions Germany GmbH, GF: Felix Imend=C3=B6rffer, HRB 36809, =
AG N=C3=BCrnberg
--=20