From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f71.google.com (mail-wm0-f71.google.com [74.125.82.71]) by kanga.kvack.org (Postfix) with ESMTP id 648BA6B0003 for ; Wed, 11 Jul 2018 04:27:46 -0400 (EDT) Received: by mail-wm0-f71.google.com with SMTP id s5-v6so1351367wmc.9 for ; Wed, 11 Jul 2018 01:27:46 -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 e2-v6si12425267wrt.347.2018.07.11.01.27.44 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Jul 2018 01:27:44 -0700 (PDT) Date: Wed, 11 Jul 2018 10:27:39 +0200 From: Pavel Machek Subject: Re: [RFC PATCH v2 05/27] Documentation/x86: Add CET description Message-ID: <20180711082739.GA18919@amd> References: <20180710222639.8241-1-yu-cheng.yu@intel.com> <20180710222639.8241-6-yu-cheng.yu@intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline In-Reply-To: <20180710222639.8241-6-yu-cheng.yu@intel.com> Sender: owner-linux-mm@kvack.org List-ID: To: Yu-cheng Yu Cc: 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 --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue 2018-07-10 15:26:17, Yu-cheng Yu wrote: > Explain how CET works and the no_cet_shstk/no_cet_ibt kernel > parameters. >=20 > --- /dev/null > +++ b/Documentation/x86/intel_cet.txt > @@ -0,0 +1,250 @@ > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > +Control Flow Enforcement Technology (CET) > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D We normally use .rst for this kind of formatted text. > +[6] The implementation of the SHSTK > +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > + > +SHSTK size > +---------- > + > +A task's SHSTK is allocated from memory to a fixed size that can > +support 32 KB nested function calls; that is 256 KB for a 64-bit > +application and 128 KB for a 32-bit application. The system admin > +can change the default size. How does admin change that? We already have ulimit for stack size, should those be somehow tied together? $ ulimit -a =2E.. stack size (kbytes, -s) 8192 --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAltFv3sACgkQMOfwapXb+vJCUwCfRHq9+RCMp+u2Y1KcEeEwRWQo uw4AoKTNBubkPzJE8R3PcwGC3r8tTOI2 =YfD9 -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6--