hrtimer: Iterate only over active clock-bases
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest2 patches 3 repliesIn review
- v12 patches 6 repliesSuperseded
Changes in v2 from the cover letter
- Dropped ffs() and wrote own routine __next_bit().
Patches in v2 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | hrtimer: update '->active_bases' before calling hrtimer_force_reprogram()kernel/ | +3 | 0 replies | |
| 2/2 | hrtimer: Iterate only over active clock-baseskernel/ | +41 | 22 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Preeti U Murthy |
|---|---|
| 1/2 | R-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH V2 0/2] hrtimer: Iterate only over active clock-bases
Hi,
'active_bases' indicates which clock-base have active timers. While it is updated (almost) correctly, it is hardly used.
And so this is an attempt to improve the code that iterates over all clock-bases.
The first patch fixes a issue that will result in a bug after the second commit, and the second commit creates a macro for_each_active_base() and uses it at multiple places.
V1->V2:
- Dropped ffs() and wrote own routine __next_bit().
Viresh Kumar (2):
hrtimer: update '->active_bases' before calling
hrtimer_force_reprogram()
hrtimer: create for_each_active_base() to iterate over active
clock-bases
kernel/time/hrtimer.c | 70 ++++++++++++++++++++++++++++++++------------------- 1 file changed, 44 insertions(+), 26 deletions(-)
Signature · 1 line
2.3.0.rc0.44.ga94655d