From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-f71.google.com (mail-wr1-f71.google.com [209.85.221.71]) by kanga.kvack.org (Postfix) with ESMTP id 809FD6B0007 for ; Fri, 13 Jul 2018 02:28:07 -0400 (EDT) Received: by mail-wr1-f71.google.com with SMTP id z16-v6so5058013wrs.22 for ; Thu, 12 Jul 2018 23:28:07 -0700 (PDT) Received: from atrey.karlin.mff.cuni.cz (atrey.karlin.mff.cuni.cz. [195.113.26.193]) by mx.google.com with ESMTPS id u16-v6si22668148wrb.128.2018.07.12.23.28.06 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Jul 2018 23:28:06 -0700 (PDT) Date: Fri, 13 Jul 2018 08:28:04 +0200 From: Pavel Machek Subject: Re: [RFC PATCH v2 25/27] x86/cet: Add PTRACE interface for CET Message-ID: <20180713062804.GA6905@amd> References: <20180710222639.8241-1-yu-cheng.yu@intel.com> <20180710222639.8241-26-yu-cheng.yu@intel.com> <20180711102035.GB8574@gmail.com> <1531323638.13297.24.camel@intel.com> <20180712140327.GA7810@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <20180712140327.GA7810@gmail.com> Sender: owner-linux-mm@kvack.org List-ID: To: Ingo Molnar Cc: Yu-cheng Yu , x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Arnd Bergmann , Andy Lutomirski , Balbir Singh , Cyrill Gorcunov , Dave Hansen , Florian Weimer , "H.J. Lu" , Jann Horn , Jonathan Corbet , Kees Cook , Mike Kravetz , Nadav Amit , Oleg Nesterov , Peter Zijlstra , "Ravi V. Shankar" , Vedvyas Shanbhogue --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > > > to "CET" (which is a well-known acronym for "Central European Time"), > > > not to CFE? > > >=20 > >=20 > > I don't know if I can change that, will find out. >=20 > So what I'd suggest is something pretty simple: to use CFT/cft in kernel = internal=20 > names, except for the Intel feature bit and any MSR enumeration which can= be CET=20 > if Intel named it that way, and a short comment explaining the acronym di= fference. >=20 > Or something like that. Actually, I don't think CFT is much better -- there's limited number of TLAs (*). "ENFORCE_FLOW"? "FLOWE"? "EFLOW"? Pavel (*) Three letter accronyms. --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltIRnQACgkQMOfwapXb+vJRBACbBpRDlJCr67dR/rk3Htvd60uk 2z0AoJRrkyCatIQBwROh41c0B0Qw/Luu =9cvN -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v--