[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20210427082537.611978720@linutronix.de>
Date: Tue, 27 Apr 2021 10:25:37 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: LKML <linux-kernel@...r.kernel.org>
Cc: Anna-Maria Behnsen <anna-maria@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Frederic Weisbecker <frederic@...nel.org>,
Peter Xu <peterx@...hat.com>,
Nitesh Narayan Lal <nitesh@...hat.com>,
Alex Belits <abelits@...vell.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
John Stultz <john.stultz@...aro.org>
Subject: [patch 0/8] hrtimers: Overhaul the clock_was_set() logic
A recent patch from Marcelo to avoid IPIs when the clock was set
https://lore.kernel.org/r/20210407135301.GA16985@fuller.cnet
made me look deeper into this.
That mechanism has caught some dust and bitrot over time and just making
clock_was_set() a little bit smarter does not make the code any better.
The following series addresses this by:
- Fixing the cases where the clock_was_set() handling is incorrect
depending on configuration or runtime conditions.
- Distangle the resume notification and the clock-was-set mechanism
to prepare for IPI avoidance
- Adopt Marcelo's patch to the modified code and add some more smarts on
top.
The series is also available from git:
git://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git hrtimer
Thanks,
tglx
---
fs/timerfd.c | 16 +++
include/linux/hrtimer.h | 8 -
kernel/time/hrtimer.c | 217 ++++++++++++++++++++++++++++++++------------
kernel/time/tick-common.c | 7 +
kernel/time/tick-internal.h | 12 ++
kernel/time/timekeeping.c | 36 ++++---
6 files changed, 219 insertions(+), 77 deletions(-)
Powered by blists - more mailing lists