-
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.
Merge branch 'x86-vdso-for-linus' of git://git.kernel.org/pub/scm/lin…
…ux/kernel/git/tip/linux-2.6-tip * 'x86-vdso-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip: x86: vdso: Remove unused variable x86-64: Optimize vDSO time() x86-64: Add time to vDSO x86-64: Turn off -pg and turn on -foptimize-sibling-calls for vDSO x86-64: Move vread_tsc into a new file with sensible options x86-64: Vclock_gettime(CLOCK_MONOTONIC) can't ever see nsec < 0 x86-64: Don't generate cmov in vread_tsc x86-64: Remove unnecessary barrier in vread_tsc x86-64: Clean up vdso/kernel shared variables
- Loading branch information
Showing
18 changed files
with
202 additions
and
185 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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
/* This code runs in userspace. */ | ||
|
||
#define DISABLE_BRANCH_PROFILING | ||
#include <asm/vgtod.h> | ||
|
||
notrace cycle_t __vsyscall_fn vread_tsc(void) | ||
{ | ||
cycle_t ret; | ||
u64 last; | ||
|
||
/* | ||
* Empirically, a fence (of type that depends on the CPU) | ||
* before rdtsc is enough to ensure that rdtsc is ordered | ||
* with respect to loads. The various CPU manuals are unclear | ||
* as to whether rdtsc can be reordered with later loads, | ||
* but no one has ever seen it happen. | ||
*/ | ||
rdtsc_barrier(); | ||
ret = (cycle_t)vget_cycles(); | ||
|
||
last = VVAR(vsyscall_gtod_data).clock.cycle_last; | ||
|
||
if (likely(ret >= last)) | ||
return ret; | ||
|
||
/* | ||
* GCC likes to generate cmov here, but this branch is extremely | ||
* predictable (it's just a funciton of time and the likely is | ||
* very likely) and there's a data dependence, so force GCC | ||
* to generate a branch instead. I don't barrier() because | ||
* we don't actually need a barrier, and if this function | ||
* ever gets inlined it will generate worse code. | ||
*/ | ||
asm volatile (""); | ||
return last; | ||
} |
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.