From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Garnier <thgarnie@google.com>
Cc: "Nicolas Pitre" <nicolas.pitre@linaro.org>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Michal Hocko" <mhocko@suse.com>,
"kvm list" <kvm@vger.kernel.org>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Christopher Li" <sparse@chrisli.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"David Howells" <dhowells@redhat.com>,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
"Pavel Machek" <pavel@ucw.cz>, "H . Peter Anvin" <hpa@zytor.com>,
"Kernel Hardening" <kernel-hardening@lists.openwall.com>,
"Christoph Lameter" <cl@linux.com>,
"Ingo Molnar" <mingo@kernel.org>,
"Kees Cook" <keescook@chromium.org>,
"the arch/x86 maintainers" <x86@kernel.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Matthew Wilcox" <mawilcox@microsoft.com>,
"Peter Foley" <pefoley2@pefoley.com>
Subject: Re: x86: PIE support and option to extend KASLR randomization
Date: Thu, 24 Aug 2017 21:07:00 -0400 [thread overview]
Message-ID: <20170824210700.5fd3b5a0@gandalf.local.home> (raw)
In-Reply-To: <CAJcbSZGhvwt=5ERtBHLJnwS=6AXBZLTMfrafzeUCqYy=-MKWDg@mail.gmail.com>
On Thu, 24 Aug 2017 14:13:38 -0700
Thomas Garnier <thgarnie@google.com> wrote:
> With the fix for function tracing, the hackbench results have an
> average of +0.8 to +1.4% (from +8% to +10% before). With a default
> configuration, the numbers are closer to 0.8%.
Wow, an empty fentry function not "nop"ed out only added 8% to 10%
overhead. I never did the benchmarks of that since I did it before
fentry was introduced, which was with the old "mcount". That gave an
average of 13% overhead in hackbench.
-- Steve
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-25 1:07 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 17:25 x86: PIE support and option to extend KASLR randomization Thomas Garnier
2017-08-10 17:25 ` [RFC v2 01/23] x86/crypto: Adapt assembly for PIE support Thomas Garnier
2017-08-10 17:25 ` [RFC v2 02/23] x86: Use symbol name on bug table " Thomas Garnier
2017-08-10 17:25 ` [RFC v2 03/23] x86: Use symbol name in jump " Thomas Garnier
2017-08-10 17:25 ` [RFC v2 04/23] x86: Add macro to get symbol address " Thomas Garnier
2017-08-10 17:25 ` [RFC v2 05/23] xen: Adapt assembly " Thomas Garnier
2017-08-10 17:25 ` [RFC v2 06/23] kvm: " Thomas Garnier
2017-08-10 17:25 ` [RFC v2 07/23] x86: relocate_kernel - " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 08/23] x86/entry/64: " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 09/23] x86: pm-trace - " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 10/23] x86/CPU: " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 11/23] x86/acpi: " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 12/23] x86/boot/64: " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 13/23] x86/power/64: " Thomas Garnier
2017-08-11 12:36 ` Pavel Machek
2017-08-11 15:09 ` Thomas Garnier
2017-08-10 17:26 ` [RFC v2 14/23] x86/paravirt: " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 15/23] x86/boot/64: Use _text in a global " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 16/23] x86/percpu: Adapt percpu " Thomas Garnier
2017-08-10 17:26 ` [RFC v2 17/23] compiler: Option to default to hidden symbols Thomas Garnier
2017-08-10 17:26 ` [RFC v2 18/23] x86/relocs: Handle DYN relocations for PIE support Thomas Garnier
2017-08-10 17:26 ` [RFC v2 19/23] x86: Support global stack cookie Thomas Garnier
2017-08-10 17:26 ` [RFC v2 20/23] x86/pie: Add option to build the kernel as PIE for x86_64 Thomas Garnier
2017-08-10 17:26 ` [RFC v2 21/23] x86/relocs: Add option to generate 64-bit relocations Thomas Garnier
2017-08-10 17:26 ` [RFC v2 22/23] x86/module: Add support for mcmodel large and PLTs Thomas Garnier
2017-08-10 17:26 ` [RFC v2 23/23] x86/kaslr: Add option to extend KASLR range from 1GB to 3GB Thomas Garnier
2017-08-11 12:41 ` x86: PIE support and option to extend KASLR randomization Ingo Molnar
2017-08-11 15:09 ` Thomas Garnier
2017-08-15 7:56 ` Ingo Molnar
2017-08-15 14:20 ` Thomas Garnier
2017-08-15 14:47 ` Daniel Micay
2017-08-15 14:58 ` Thomas Garnier
2017-08-16 15:12 ` Ingo Molnar
2017-08-16 16:09 ` Christopher Lameter
2017-08-16 16:26 ` Daniel Micay
2017-08-16 16:32 ` Ard Biesheuvel
2017-08-16 16:57 ` Thomas Garnier
2017-08-17 8:09 ` Ingo Molnar
2017-08-17 14:10 ` Thomas Garnier
2017-08-24 21:13 ` Thomas Garnier
2017-08-24 21:42 ` Linus Torvalds
2017-08-25 15:35 ` Thomas Garnier
2017-08-25 1:07 ` Steven Rostedt [this message]
2017-08-25 8:04 ` Ingo Molnar
2017-08-25 15:05 ` Thomas Garnier
2017-08-29 19:34 ` Thomas Garnier
2017-09-21 15:59 ` Ingo Molnar
2017-09-21 16:10 ` Ard Biesheuvel
2017-09-21 21:21 ` Thomas Garnier
2017-09-22 4:24 ` Markus Trippelsdorf
2017-09-22 14:38 ` Thomas Garnier
2017-09-22 23:55 ` Thomas Garnier
2017-09-21 21:16 ` Thomas Garnier
2017-09-22 0:06 ` Thomas Garnier
2017-09-22 16:32 ` Ingo Molnar
2017-09-22 18:08 ` Thomas Garnier
2017-09-23 9:43 ` Ingo Molnar
2017-10-02 20:28 ` Thomas Garnier
2017-09-22 18:38 ` H. Peter Anvin
2017-09-22 18:57 ` Kees Cook
2017-09-22 19:06 ` H. Peter Anvin
2017-09-22 18:59 ` Thomas Garnier
2017-09-23 9:49 ` Ingo Molnar
2017-08-17 14:12 ` Boris Lukashev
2017-08-25 15:38 ` Christopher Lameter
2017-08-27 22:39 ` Boris Lukashev
2017-08-28 9:59 ` Pavel Machek
2017-08-21 13:32 ` Peter Zijlstra
2017-08-21 14:28 ` Peter Zijlstra
2017-09-22 18:27 ` H. Peter Anvin
2017-09-23 10:00 ` Ingo Molnar
2017-09-24 22:37 ` Pavel Machek
2017-09-25 7:33 ` Ingo Molnar
2017-10-06 10:39 ` Pavel Machek
2017-10-20 8:13 ` Ingo Molnar
2017-08-21 14:31 ` Peter Zijlstra
2017-08-21 15:57 ` Thomas Garnier
2017-08-28 1:26 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2017-10-04 21:19 Thomas Garnier
2017-07-18 22:33 Thomas Garnier
2017-07-19 14:08 ` Christopher Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170824210700.5fd3b5a0@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=ast@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cl@linux.com \
--cc=daniel@iogearbox.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kvm@vger.kernel.org \
--cc=mawilcox@microsoft.com \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=paul.gortmaker@windriver.com \
--cc=pavel@ucw.cz \
--cc=pefoley2@pefoley.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=sparse@chrisli.org \
--cc=thgarnie@google.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).