* Ingo Molnar <mingo@xxxxxxxxxx> wrote:
> > 0.10% [kernel] [k] __do_page_fault
> > 0.08% [kernel] [k] handle_mm_fault
> > 0.08% libjvm.so [.] os::javaTimeMillis()
> > 0.08% [kernel] [k] emulate_vsyscall
>
> Oh, finally a clue: you seem to have vsyscall emulation
> overhead!
>
> Vsyscall emulation is fundamentally page fault driven - which
> might explain why you are seeing page fault overhead. It might
> also interact with other sources of faults - such as
> numa/core's working set probing ...
>
> Many JVMs try to be smart with the vsyscall. As a test, does
> the vsyscall=native boot option change the results/behavior in
> any way?
As a blind shot into the dark, does the attached patch help?
If that's the root cause then it should measurably help mainline
SPECjbb performance as well. It could turn numa/core from a
regression into a win on your system.
Thanks,
Ingo
----------------->
Subject: x86/vsyscall: Add Kconfig option to use native vsyscalls, switch to it
From: Ingo Molnar <mingo@xxxxxxxxxx>
Apparently there's still plenty of systems out there triggering
the vsyscall emulation page faults - causing hard to track down
performance regressions on page fault intense workloads...
Some people seem to have run into that with threading-intense
Java workloads.
So until there's a better solution to this, add a Kconfig switch
to make the vsyscall mode configurable and turn native vsyscall
support back on by default.
Distributions whose libraries and applications use the vDSO and never
access the vsyscall page can change the config option to off.
Note, I don't think we want to expose the "none" option via a Kconfig
switch - it breaks the ABI. So it's "native" versus "emulate", with
"none" being available as a kernel boot option, for the super paranoid.
For more background, see these upstream commits:
3ae36655b97a x86-64: Rework vsyscall emulation and add vsyscall= parameter
5cec93c216db x86-64: Emulate legacy vsyscalls
Cc: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
Cc: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Ingo Molnar <mingo@xxxxxxxxxx>
---
arch/x86/Kconfig | 21 +++++++++++++++++++++
arch/x86/kernel/vsyscall_64.c | 8 +++++++-
2 files changed, 28 insertions(+), 1 deletion(-)
Index: linux/arch/x86/Kconfig
===================================================================
--- linux.orig/arch/x86/Kconfig
+++ linux/arch/x86/Kconfig
@@ -2234,6 +2234,27 @@ config X86_X32
elf32_x86_64 support enabled to compile a kernel with this
option set.
+config X86_VSYSCALL_COMPAT
+ bool "vsyscall compatibility"
+ default y
+ help
+ vsyscalls, as global executable pages, can be a security hole
+ escallation helper by exposing an easy shell code target with
+ a predictable address.
+
+ Many versions of glibc rely on the vsyscall page though, so it
+ cannot be eliminated unconditionally. If you disable this
+ option these systems will still work but might incur the overhead
+ of vsyscall emulation page faults.
+
+ The vsyscall=none, vsyscall=emulate, vsyscall=native kernel boot
+ option can be used to override this mode as well.
+
+ Keeping this option enabled leaves the vsyscall page enabled,
+ i.e. vsyscall=native. Disabling this option means vsyscall=emulate.
+
+ If unsure, say Y.
+
config COMPAT
def_bool y
depends on IA32_EMULATION || X86_X32
Index: linux/arch/x86/kernel/vsyscall_64.c
===================================================================
--- linux.orig/arch/x86/kernel/vsyscall_64.c
+++ linux/arch/x86/kernel/vsyscall_64.c
@@ -56,7 +56,13 @@
DEFINE_VVAR(int, vgetcpu_mode);
DEFINE_VVAR(struct vsyscall_gtod_data, vsyscall_gtod_data);
-static enum { EMULATE, NATIVE, NONE } vsyscall_mode = EMULATE;
+static enum { EMULATE, NATIVE, NONE } vsyscall_mode =
+#ifdef CONFIG_X86_VSYSCALL_COMPAT
+ NATIVE
+#else
+ EMULATE
+#endif
+;
static int __init vsyscall_setup(char *str)
{
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>