[PATCH 7/8] s390: time: Provide read_boot_clock64() and read_persistent_clock64()

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org As part of addressing y2038 problem for in-kernel uses, this patch converts read_boot_clock() to read_boot_clock64() and read_persistent_clock() to read_persistent_clock64() using timespec64. Since S390 is a 64bit architecture, also rename some timespec

[PATCH 6/8] ARM: time: Provide read_boot_clock64() and read_persistent_clock64()

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org As part of addressing y2038 problem for in-kernel uses, this patch converts read_boot_clock() to read_boot_clock64() and read_persistent_clock() to read_persistent_clock64() using timespec64 by converting clock_access_fn to use timespec64. Signed-off

[PATCH 5/8] ARM: tegra: clock: Provide y2038-safe tegra_read_persistent_clock() replacement

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org As part of addressing y2038 problem for in-kernel uses, this patch adds the y2038-safe tegra_read_persistent_clock64() using timespec64. Because we rely on some subsequent changes to convert arm multiarch support, tegra_read_persistent_clock

[PATCH 0/8] Add y2038 safe replacements for read_boot_clock(), read_persistent_clock() and update_persistent_clock()

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org read_boot_clock(), read_persistent_clock() and update_persistent_clock() all use timespec which may have y2038 problem, thus we are planning on converting all of them to use timespec64. The approach we're using is: 1) First of all, add the __weak

[PATCH 8/8] time: Remove read_boot_clock()

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org Now we have all the read_boot_clock64() for all implementations, it's time to remove read_boot_clock() completely from the kernel. Signed-off-by: Xunlei Pang pang.xun...@linaro.org --- read_persistent_clock() and update_persistent_clock() are way more

[PATCH 1/8] time: Add y2038 safe read_boot_clock64()

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org As part of addressing in-kernel y2038 issues, this patch adds read_boot_clock64() and replaces all the call sites of read_boot_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe read_boot_clock

[PATCH 2/8] time: Add y2038 safe read_persistent_clock64()

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org As part of addressing in-kernel y2038 issues, this patch adds read_persistent_clock64() and replaces all the call sites of read_persistent_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe

[PATCH 3/8] time: Add y2038 safe update_persistent_clock64()

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org As part of addressing in-kernel y2038 issues, this patch adds update_persistent_clock64() and replaces all the call sites of update_persistent_clock() with this function. This is a __weak implementation, which simply calls the existing y2038 unsafe

[PATCH 4/8] ARM: OMAP: 32k counter: Provide y2038-safe omap_read_persistent_clock() replacement

2015-03-10 Thread Xunlei Pang
From: Xunlei Pang pang.xun...@linaro.org As part of addressing y2038 problem for in-kernel uses, this patch adds the y2038-safe omap_read_persistent_clock64() using timespec64. Because we rely on some subsequent changes to convert arm multiarch support, omap_read_persistent_clock