public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Anna-Maria Behnsen <anna-maria@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>
Subject: [GIT PULL] Timer subsystem changes for v6.8
Date: Mon, 8 Jan 2024 11:44:00 +0100	[thread overview]
Message-ID: <ZZvR8LSj0ea7XZ9+@gmail.com> (raw)

Linus,

Please pull the latest timers/core git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-2024-01-08

   # HEAD: da65f29dada7f7cbbf0d6375b88a0316f5f7d6f5 timers: Fix nextevt calculation when no timers are pending

Timer subsystem changes for v6.8:

 - Various preparatory cleanups & enhancements of the timer-wheel code,
   in preparation for the WIP 'pull timers at expiry' timer migration model
   series (which will replace the current 'push timers at enqueue' migration
   model), by Anna-Maria Behnsen:

      - Update comments and clean up confusing variable names

      - Add debug check to warn about time travel

      - Improve/expand timer-wheel tracepoints

      - Optimize away unnecessary IPIs for deferrable timers

      - Restructure & clean up next_expiry_recalc()

      - Clean up forward_timer_base()

      - Introduce __forward_timer_base() and use it to simplify
        and micro-optimize get_next_timer_interrupt()

 - Restructure the get_next_timer_interrupt()'s idle logic
   for better readability and to enable a minor optimization.

 - Fix the nextevt calculation when no timers are pending

 - Fix the sysfs_get_uname() prototype declaration

 Thanks,

	Ingo

------------------>
Anna-Maria Behnsen (11):
      tick-sched: Fix function names in comments
      tick/sched: Cleanup confusing variables
      tick-sched: Warn when next tick seems to be in the past
      tracing/timers: Enhance timer_start tracepoint
      tracing/timers: Add tracepoint for tracking timer base is_idle flag
      timers: Do not IPI for deferrable timers
      timers: Move store of next event into __next_timer_interrupt()
      timers: Clarify check in forward_timer_base()
      timers: Split out forward timer base functionality
      timers: Use already existing function for forwarding timer base
      timers: Fix nextevt calculation when no timers are pending

Arnd Bergmann (1):
      time: Make sysfs_get_uname() function visible in header

Thomas Gleixner (1):
      timers: Rework idle logic


 include/trace/events/timer.h |  40 +++++++++++----
 kernel/time/tick-internal.h  |   3 +-
 kernel/time/tick-sched.c     |  25 ++++++----
 kernel/time/timer.c          | 116 ++++++++++++++++++++++++-------------------
 4 files changed, 112 insertions(+), 72 deletions(-)

             reply	other threads:[~2024-01-08 10:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 10:44 Ingo Molnar [this message]
2024-01-09  4:04 ` [GIT PULL] Timer subsystem changes for v6.8 pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZZvR8LSj0ea7XZ9+@gmail.com \
    --to=mingo@kernel.org \
    --cc=anna-maria@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox