From: Christopher Lameter Subject: Re: x86: PIE support and option to extend KASLR randomization Date: Wed, 19 Jul 2017 09:08:55 -0500 (CDT) Message-ID: References: <20170718223333.110371-1-thgarnie@google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: Herbert Xu , "David S . Miller" , Thomas Gleixner , Ingo Molnar , "H . Peter Anvin" , Peter Zijlstra , Josh Poimboeuf , Arnd Bergmann , Matthias Kaehlcke , Boris Ostrovsky , Juergen Gross , Paolo Bonzini , =?ISO-8859-2?Q?Radim_Kr=E8m=E1=F8?= , Joerg Roedel , Andy Lutomirski , Borislav Petkov , "Kirill A . Shutemov" , Brian Gerst , Borislav Petkov , Christian Borntraeger , "Rafael J . Wysocki" , Len Brow To: Thomas Garnier Return-path: List-Post: List-Help: List-Unsubscribe: List-Subscribe: In-Reply-To: <20170718223333.110371-1-thgarnie@google.com> List-Id: linux-crypto.vger.kernel.org On Tue, 18 Jul 2017, Thomas Garnier wrote: > Performance/Size impact: > Hackbench (50% and 1600% loads): > - PIE enabled: 7% to 8% on half load, 10% on heavy load. > slab_test (average of 10 runs): > - PIE enabled: 3% to 4% > Kernbench (average of 10 Half and Optimal runs): > - PIE enabled: 5% to 6% > > Size of vmlinux (Ubuntu configuration): > File size: > - PIE disabled: 472928672 bytes (-0.000169% from baseline) > - PIE enabled: 216878461 bytes (-54.14% from baseline) Maybe we need something like CONFIG_PARANOIA so that we can determine at build time how much performance we want to sacrifice for performance? Its going to be difficult to understand what all these hardening config options do.