[PATCH 0/8] Add y2038 safe replacements for read_boot_clock(), read_persistent_clock() and update_persistent_clock()
From: Xunlei Pang
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" implementaion of xxx_clock64() which uses
xxx_clock() and timespec64.
Let's take read_persistent_clock() as an example. We can create its
y2038-safe version below:
void __weak read_persistent_clock64(struct timespec64 *ts64)
{
struct timespec ts;
read_persistent_clock();
*ts64 = timespec_to_timespec64(ts);
}
Then, replace all the call sites of xxx_clock() with xxx_clock64() except
the one used by xxx_clock64().
2) Convert every architecture specific xxx_clock() to xxx_clock64() one by one.
At this point, we can convert the three functions at a time if needed,
because
most time they're correlated.
3) Remove xxx_clock() after all its architecture specific implementations have
been
converted to use corresponding y2038 safe xxx_clock64().
This patchset firstly finished the step1 for all the three functions, then
focused
on read_boot_clock() which is simple to go on with step2 and step3 as a whole
show.
As for read_persistent_clock() and update_persistent_clock() which are more
complex,
requiring many efforts to convert every architecture specific implementation
gradually.
The approach used here is Suggested-by: "Arnd Bergmann "
Xunlei Pang (8):
time: Add y2038 safe read_boot_clock64()
time: Add y2038 safe read_persistent_clock64()
time: Add y2038 safe update_persistent_clock64()
ARM: OMAP: 32k counter: Provide y2038-safe
omap_read_persistent_clock() replacement
ARM: tegra: clock: Provide y2038-safe tegra_read_persistent_clock()
replacement
ARM: time: Provide read_boot_clock64() and read_persistent_clock64()
s390: time: Provide read_boot_clock64() and read_persistent_clock64()
time: Remove read_boot_clock()
arch/arm/include/asm/mach/time.h| 3 +--
arch/arm/kernel/time.c | 6 +++---
arch/arm/plat-omap/counter_32k.c| 18 ++
arch/mips/lasat/sysctl.c| 4 ++--
arch/s390/include/asm/timex.h | 4 ++--
arch/s390/kernel/debug.c| 4 ++--
arch/s390/kernel/time.c | 6 +++---
drivers/clocksource/tegra20_timer.c | 15 +++
drivers/rtc/systohc.c | 2 +-
include/linux/timekeeping.h | 4 +++-
kernel/time/ntp.c | 13 -
kernel/time/timekeeping.c | 31 ---
12 files changed, 58 insertions(+), 52 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH 0/8] Add y2038 safe replacements for read_boot_clock(), read_persistent_clock() and update_persistent_clock()
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 implementaion of xxx_clock64() which uses
xxx_clock() and timespec64.
Let's take read_persistent_clock() as an example. We can create its
y2038-safe version below:
void __weak read_persistent_clock64(struct timespec64 *ts64)
{
struct timespec ts;
read_persistent_clock(ts);
*ts64 = timespec_to_timespec64(ts);
}
Then, replace all the call sites of xxx_clock() with xxx_clock64() except
the one used by xxx_clock64().
2) Convert every architecture specific xxx_clock() to xxx_clock64() one by one.
At this point, we can convert the three functions at a time if needed,
because
most time they're correlated.
3) Remove xxx_clock() after all its architecture specific implementations have
been
converted to use corresponding y2038 safe xxx_clock64().
This patchset firstly finished the step1 for all the three functions, then
focused
on read_boot_clock() which is simple to go on with step2 and step3 as a whole
show.
As for read_persistent_clock() and update_persistent_clock() which are more
complex,
requiring many efforts to convert every architecture specific implementation
gradually.
The approach used here is Suggested-by: Arnd Bergmann a...@arndb.de
Xunlei Pang (8):
time: Add y2038 safe read_boot_clock64()
time: Add y2038 safe read_persistent_clock64()
time: Add y2038 safe update_persistent_clock64()
ARM: OMAP: 32k counter: Provide y2038-safe
omap_read_persistent_clock() replacement
ARM: tegra: clock: Provide y2038-safe tegra_read_persistent_clock()
replacement
ARM: time: Provide read_boot_clock64() and read_persistent_clock64()
s390: time: Provide read_boot_clock64() and read_persistent_clock64()
time: Remove read_boot_clock()
arch/arm/include/asm/mach/time.h| 3 +--
arch/arm/kernel/time.c | 6 +++---
arch/arm/plat-omap/counter_32k.c| 18 ++
arch/mips/lasat/sysctl.c| 4 ++--
arch/s390/include/asm/timex.h | 4 ++--
arch/s390/kernel/debug.c| 4 ++--
arch/s390/kernel/time.c | 6 +++---
drivers/clocksource/tegra20_timer.c | 15 +++
drivers/rtc/systohc.c | 2 +-
include/linux/timekeeping.h | 4 +++-
kernel/time/ntp.c | 13 -
kernel/time/timekeeping.c | 31 ---
12 files changed, 58 insertions(+), 52 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
