From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (193.142.43.55:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 01 Nov 2019 13:16:08 -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 ) id 1iQWmc-0000TC-Q6 for speck@linutronix.de; Fri, 01 Nov 2019 14:16:07 +0100 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id BA88CB3A1 for ; Fri, 1 Nov 2019 13:15:59 +0000 (UTC) Date: Fri, 1 Nov 2019 14:15:48 +0100 From: Borislav Petkov Subject: [MODERATED] Re: [PATCH 3/9] TAA 3 Message-ID: <20191101131548.GB32677@nazgul.tnic> References: <580e02757c3e639bff00fcea830aa46eba46a92f.1571905227.git.bp@suse.de> <20191030132858.GA703436@kroah.com> <20191030172402.GB9730@guptapadev.amr> <20191030192758.GD709410@kroah.com> <20191030194440.GP31513@dhcp22.suse.cz> <20191101093526.GA2758611@kroah.com> MIME-Version: 1.0 In-Reply-To: <20191101093526.GA2758611@kroah.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To: speck@linutronix.de List-ID: On Fri, Nov 01, 2019 at 10:35:26AM +0100, speck for Greg KH wrote: > Anyway, yes, TM shoudl have the same semantic. But, if it's too late at > the moment, we can always unify this later on if PPC really wants it. We can s/unify/add additional/ to minimize confusion. What I mean is, we can add "tm=3D" as an additional option which coexists with the "tsx=3D" option on x86 because the patches would have released already and we would have communicated "tsx=3D" to people by then. So "tsx=3D" and "tm=3D" would do the same thing on x86. Methinks. --=20 Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imend=C3=B6rffer, Mary Higgins, Sri Rasiah, HRB 21= 284 (AG N=C3=BCrnberg) --=20