diff options
Diffstat (limited to 'patches/time-hrtimer-use-a-MONOTIC-clock-for-relative-REALTI.patch')
| -rw-r--r-- | patches/time-hrtimer-use-a-MONOTIC-clock-for-relative-REALTI.patch | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/patches/time-hrtimer-use-a-MONOTIC-clock-for-relative-REALTI.patch b/patches/time-hrtimer-use-a-MONOTIC-clock-for-relative-REALTI.patch deleted file mode 100644 index 829fb928a733..000000000000 --- a/patches/time-hrtimer-use-a-MONOTIC-clock-for-relative-REALTI.patch +++ /dev/null @@ -1,26 +0,0 @@ -From: Sebastian Andrzej Siewior <bigeasy@linutronix.de> -Date: Wed, 11 Oct 2017 10:23:00 +0200 -Subject: [PATCH] time/hrtimer: use a MONOTIC clock for "relative" REALTIME - sleep - -clock_nanosleep(CLOCK_REALTIME, ) with a relative delay/time should not -be effected by clock_settime(CLOCK_REALTIME,) thus we need to use -CLOCK_MONOTONIC instead. This is already done for the clock itself and -for the SOFT-irq based clock but was forgotten for the HARD-irq clock. - -Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de> ---- - kernel/time/hrtimer.c | 2 ++ - 1 file changed, 2 insertions(+) - ---- a/kernel/time/hrtimer.c -+++ b/kernel/time/hrtimer.c -@@ -1234,6 +1234,8 @@ static void __hrtimer_init(struct hrtime - clock_id = CLOCK_MONOTONIC; - else if (clock_id == CLOCK_REALTIME_SOFT) - clock_id = CLOCK_MONOTONIC_SOFT; -+ else if (clock_id == CLOCK_REALTIME_HARD) -+ clock_id = CLOCK_MONOTONIC_HARD; - } - - base = hrtimer_clockid_to_base(clock_id); |