-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
x86-64: Clean up vdso/kernel shared variables
Variables that are shared between the vdso and the kernel are currently a bit of a mess. They are each defined with their own magic, they are accessed differently in the kernel, the vsyscall page, and the vdso, and one of them (vsyscall_clock) doesn't even really exist. This changes them all to use a common mechanism. All of them are delcared in vvar.h with a fixed address (validated by the linker script). In the kernel (as before), they look like ordinary read-write variables. In the vsyscall page and the vdso, they are accessed through a new macro VVAR, which gives read-only access. The vdso is now loaded verbatim into memory without any fixups. As a side bonus, access from the vdso is faster because a level of indirection is removed. While we're at it, pack jiffies and vgetcpu_mode into the same cacheline. Signed-off-by: Andy Lutomirski <luto@mit.edu> Cc: Andi Kleen <andi@firstfloor.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: "David S. Miller" <davem@davemloft.net> Cc: Eric Dumazet <eric.dumazet@gmail.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Borislav Petkov <bp@amd64.org> Link: http://lkml.kernel.org/r/%3C7357882fbb51fa30491636a7b6528747301b7ee9.1306156808.git.luto%40mit.edu%3E Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
- Loading branch information
Andy Lutomirski
authored and
Thomas Gleixner
committed
May 24, 2011
1 parent
d762f43
commit 8c49d9a
Showing
15 changed files
with
91 additions
and
145 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,52 @@ | ||
/* | ||
* vvar.h: Shared vDSO/kernel variable declarations | ||
* Copyright (c) 2011 Andy Lutomirski | ||
* Subject to the GNU General Public License, version 2 | ||
* | ||
* A handful of variables are accessible (read-only) from userspace | ||
* code in the vsyscall page and the vdso. They are declared here. | ||
* Some other file must define them with DEFINE_VVAR. | ||
* | ||
* In normal kernel code, they are used like any other variable. | ||
* In user code, they are accessed through the VVAR macro. | ||
* | ||
* Each of these variables lives in the vsyscall page, and each | ||
* one needs a unique offset within the little piece of the page | ||
* reserved for vvars. Specify that offset in DECLARE_VVAR. | ||
* (There are 896 bytes available. If you mess up, the linker will | ||
* catch it.) | ||
*/ | ||
|
||
/* Offset of vars within vsyscall page */ | ||
#define VSYSCALL_VARS_OFFSET (3072 + 128) | ||
|
||
#if defined(__VVAR_KERNEL_LDS) | ||
|
||
/* The kernel linker script defines its own magic to put vvars in the | ||
* right place. | ||
*/ | ||
#define DECLARE_VVAR(offset, type, name) \ | ||
EMIT_VVAR(name, VSYSCALL_VARS_OFFSET + offset) | ||
|
||
#else | ||
|
||
#define DECLARE_VVAR(offset, type, name) \ | ||
static type const * const vvaraddr_ ## name = \ | ||
(void *)(VSYSCALL_START + VSYSCALL_VARS_OFFSET + (offset)); | ||
|
||
#define DEFINE_VVAR(type, name) \ | ||
type __vvar_ ## name \ | ||
__attribute__((section(".vsyscall_var_" #name), aligned(16))) | ||
|
||
#define VVAR(name) (*vvaraddr_ ## name) | ||
|
||
#endif | ||
|
||
/* DECLARE_VVAR(offset, type, name) */ | ||
|
||
DECLARE_VVAR(0, volatile unsigned long, jiffies) | ||
DECLARE_VVAR(8, int, vgetcpu_mode) | ||
DECLARE_VVAR(128, struct vsyscall_gtod_data, vsyscall_gtod_data) | ||
|
||
#undef DECLARE_VVAR | ||
#undef VSYSCALL_VARS_OFFSET |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.