hrtimer: Reprogramming and clock_was_set() overhaul
Status from this message: The following commit has been merged into the timers/core branch of tip:
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest10 patches 9 repliesApplied
- v11 patch 6 repliesSuperseded
Changes in v2 from the cover letter
- Pick up Peter's consolidation patch
- Polish a few things
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/10 | hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns()kernel/ | +53 | 0 replies | |
| 2/10 | hrtimer: Consolidate reprogramming codekernel/ | +29 | 13 replies | |
| 3/10 | hrtimer: Ensure timerfd notification for HIGHRES=ninclude/ kernel/ kernel/ | +19 | 0 replies | |
| 4/10 | hrtimer: Force clock_was_set() handling for the HIGHRES=n, NOHZ=y casekernel/ | +59 | 0 replies | |
| 5/10 | timerfd: Provide timerfd_resume()fs/ include/ | +18 | 0 replies | |
| 6/10 | timekeeping: Distangle resume and clock-was-set eventsinclude/ kernel/ kernel/ +2 more | +18 | 0 replies | |
| 7/10 | time/timekeeping: Avoid invoking clock_was_set() twicekernel/ | +10 | 0 replies | |
| 8/10 | hrtimer: Add bases argument to clock_was_set()kernel/ kernel/ kernel/ | +17 | 0 replies | |
| 9/10 | hrtimer: Avoid unnecessary SMP function calls in clock_was_set()kernel/ | +33 | 0 replies | |
| 10/10 | hrtimer: Avoid more SMP function calls in clock_was_set()kernel/ | +65 | 0 replies |
Reviews trailers per patch
None of the 10 patches has a Reviewed-by or Acked-by.
| Patch | Mike Galbraith | Marek Szyprowski |
|---|---|---|
| 1/10 | ||
| 2/10 | T-b | T-b |
| 3/10 | ||
| 4/10 | ||
| 5/10 | ||
| 6/10 | ||
| 7/10 | ||
| 8/10 | ||
| 9/10 | ||
| 10/10 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [patch V2 00/10] hrtimer: Reprogramming and clock_was_set() overhaul
Folks!
This is the second version of the clock_was_set() overhaul together with the avoidance of double reprogramming when rearming an enqueued timer.
Version 1 of those patches can be found here:
https://lore.kernel.org/r/[email protected]
and
https://lore.kernel.org/r/[email protected]
Both the reprogramming logic and the clock_was_set() logic are not really optimized. The series addresses this.
- Avoid double reprogramming when an enqueued timer is rearmed
- Consolidate the reprogramming variants (Peter Zijlstra)
- Fix 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
Changes vs V1:
- Pick up Peter's consolidation patch
- Polish a few things
Thanks,
tglx
--- fs/timerfd.c | 16 ++ include/linux/hrtimer.h | 8 - kernel/time/hrtimer.c | 337 +++++++++++++++++++++++++++++++------------- kernel/time/tick-common.c | 7 kernel/time/tick-internal.h | 12 + kernel/time/timekeeping.c | 36 ++-- 6 files changed, 299 insertions(+), 117 deletions(-)