diff options
author | Thomas Gleixner <tglx@linutronix.de> | 2018-04-19 16:27:44 +0200 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2018-04-19 16:27:44 +0200 |
commit | 1cfd904f16740df21b2df7b41c7a0dc00cbd434c (patch) | |
tree | aa247a7d84377f5ca089199aba609fb7ab74aa7e /arch/x86/kernel/cpu/intel.c | |
parent | 87ef12027b9b1dd0e0b12cf311fbcb19f9d92539 (diff) | |
parent | 01909974b41036a6a8d3907c66cc7b41c9a73da9 (diff) | |
download | linux-1cfd904f16740df21b2df7b41c7a0dc00cbd434c.tar.gz linux-1cfd904f16740df21b2df7b41c7a0dc00cbd434c.tar.bz2 linux-1cfd904f16740df21b2df7b41c7a0dc00cbd434c.zip |
Merge tag 'y2038-timekeeping' of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground into timers/core
Pull y2038 timekeeping syscall changes from Arnd Bergmann:
This is the first set of system call entry point changes to enable 32-bit
architectures to have variants on both 32-bit and 64-bit time_t. Typically
these system calls take a 'struct timespec' argument, but that structure
is defined in user space by the C library and its layout will change.
The kernel already supports handling the 32-bit time_t on 64-bit
architectures through the CONFIG_COMPAT mechanism. As there are a total
of 51 system calls suffering from this problem, reusing that mechanism
on 32-bit architectures.
We already have patches for most of the remaining system calls, but this
set contains most of the complexity and is best tested. There was one
last-minute regression that prevented it from going into 4.17, but that
is fixed now.
More details from Deepa's patch series description:
Big picture is as per the lwn article:
https://lwn.net/Articles/643234/ [2]
The series is directed at converting posix clock syscalls:
clock_gettime, clock_settime, clock_getres and clock_nanosleep
to use a new data structure __kernel_timespec at syscall boundaries.
__kernel_timespec maintains 64 bit time_t across all execution modes.
vdso will be handled as part of each architecture when they enable
support for 64 bit time_t.
The compat syscalls are repurposed to provide backward compatibility
by using them as native syscalls as well for 32 bit architectures.
They will continue to use timespec at syscall boundaries.
CONFIG_64_BIT_TIME controls whether the syscalls use __kernel_timespec
or timespec at syscall boundaries.
The series does the following:
1. Enable compat syscalls on 32 bit architectures.
2. Add a new __kernel_timespec type to be used as the data structure
for all the new syscalls.
3. Add new config CONFIG_64BIT_TIME(intead of the CONFIG_COMPAT_TIME in
[1] and [2] to switch to new definition of __kernel_timespec. It is
the same as struct timespec otherwise.
4. Add new CONFIG_32BIT_TIME to conditionally compile compat syscalls.
Diffstat (limited to 'arch/x86/kernel/cpu/intel.c')
0 files changed, 0 insertions, 0 deletions