x86/vdso: Remove "memory" clobbers in the vDSO syscall fallbacks
authorAndy Lutomirski <luto@kernel.org>
Thu, 4 Oct 2018 21:44:43 +0000 (14:44 -0700)
committerIngo Molnar <mingo@kernel.org>
Fri, 5 Oct 2018 08:12:18 +0000 (10:12 +0200)
commit89fe0a1f1c694a3b0b3cfa8c0952d603753f36df
treeecb364f8a2faa9879744427b4708693224d34c83
parent315f28fa3a7bfbbb6233d800dffa327e87f96129
x86/vdso: Remove "memory" clobbers in the vDSO syscall fallbacks

When a vDSO clock function falls back to the syscall, no special
barriers or ordering is needed, and the syscall fallbacks don't
clobber any memory that is not explicitly listed in the asm
constraints.  Remove the "memory" clobber.

This causes minor changes to the generated code, but otherwise has
no obvious performance impact.  I think it's nice to have, though,
since it may help the optimizer in the future.

Signed-off-by: Andy Lutomirski <luto@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Link: http://lkml.kernel.org/r/3a7438f5fb2422ed881683d2ccffd7f987b2dc44.1538689401.git.luto@kernel.org
Signed-off-by: Ingo Molnar <mingo@kernel.org>
arch/x86/entry/vdso/vclock_gettime.c