Nathan Lynch 878854a374 arm64: VDSO: fix coarse clock monotonicity regression ... Since 906c55579a ("timekeeping: Copy the shadow-timekeeper over the real timekeeper last") it has become possible on arm64 to: - Obtain a CLOCK_MONOTONIC_COARSE or CLOCK_REALTIME_COARSE timestamp via syscall. - Subsequently obtain a timestamp for the same clock ID via VDSO which predates the first timestamp (by one jiffy). This is because arm64's update_vsyscall is deriving the coarse time using the __current_kernel_time interface, when it should really be using the timekeeper object provided to it by the timekeeping core. It happened to work before only because __current_kernel_time would access the same timekeeper object which had been passed to update_vsyscall. This is no longer the case. Signed-off-by: Nathan Lynch <nathan_lynch@mentor.com> Acked-by: Will Deacon <will.deacon@arm.com> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>		2015-08-10 15:37:45 +01:00
..
boot	dmaengine fixes for 4.2-rc5	2015-08-01 12:47:04 -07:00
configs
crypto
include
kernel	arm64: VDSO: fix coarse clock monotonicity regression	2015-08-10 15:37:45 +01:00
kvm
lib
mm
net
xen
Kconfig
Kconfig.debug
Makefile