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 ; 22 Oct 2019 18:12:35 -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 1iMye1-0004JG-6c for speck@linutronix.de; Tue, 22 Oct 2019 20:12:34 +0200 Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 0BD38ACC4 for ; Tue, 22 Oct 2019 18:12:27 +0000 (UTC) Date: Tue, 22 Oct 2019 20:12:15 +0200 From: Borislav Petkov Subject: [MODERATED] Re: Re: [PATCH v7 04/10] TAAv7 4 Message-ID: <20191022181215.GP31458@zn.tnic> References: <20191022165112.GK31458@zn.tnic> <20191022170230.GM31458@zn.tnic> <20191022180032.GF29216@guptapadev.amr> MIME-Version: 1.0 In-Reply-To: <20191022180032.GF29216@guptapadev.amr> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable To: speck@linutronix.de List-ID: On Tue, Oct 22, 2019 at 11:00:32AM -0700, speck for Pawan Gupta wrote: > It was called taa=3D in earlier versions. There was a feedback to change > it to tsx_async_abort=3D. I know, I'm just saying it is confusing. > tsx_async_abort is consistent with sysfs file. >=20 > /sys/devices/system/cpu/vulnerabilities/tsx_async_abort Well, that's not really an argument. --=20 Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imend=C3=B6rffer, HRB 36809, = AG N=C3=BCrnberg --=20