public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <frederic@kernel.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <frederic@kernel.org>,
	Joel Fernandes <joel@joelfernandes.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	vineethrp@gmail.com
Subject: [PATCH 0/5] tick/nohz: cleanups and fixes v2
Date: Tue, 12 Sep 2023 12:44:01 +0200	[thread overview]
Message-ID: <20230912104406.312185-1-frederic@kernel.org> (raw)

Hi,

This is a repost of https://lore.kernel.org/all/20230714120852.23573-1-frederic@kernel.org/

Just a bunch of cleanups, comment improvements and also non critical fixes.
Changes since v1:

* s/tick_lowres_handler/tick_nohz_lowres_handler (per Joel suggestion)
  s/tick_highres_handler/tick_nohz_highres_handler

* Remove tick_nohz_idle_stop_tick_protected() (Xueshi Hu)

* Fix "NOHZ tick-stop error: local softirq work is pending, handler #02!!!"
  message

Frederic Weisbecker (4):
  tick/nohz: Rename the tick handlers to more self-explanatory names
  tick/nohz: Update obsolete comments
  tick/nohz: Don't shutdown the lowres tick from itself
  timers: Tag (hr)timer softirq as hotplug safe

Xueshi Hu (1):
  tick/nohz: remove unused tick_nohz_idle_stop_tick_protected()

 include/linux/interrupt.h |  6 ++-
 include/linux/tick.h      | 10 -----
 kernel/time/tick-sched.c  | 78 ++++++++++++++++++++++++++-------------
 3 files changed, 58 insertions(+), 36 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-09-12 10:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12 10:44 Frederic Weisbecker [this message]
2023-09-12 10:44 ` [PATCH 1/5] tick/nohz: Rename the tick handlers to more self-explanatory names Frederic Weisbecker
2023-09-27 15:01   ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2023-09-12 10:44 ` [PATCH 2/5] tick/nohz: Update obsolete comments Frederic Weisbecker
2023-09-27 15:01   ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2023-09-28  9:07     ` [PATCH] tick/nohz: Update comments some more Ingo Molnar
2023-09-28  9:11       ` Ingo Molnar
2023-09-29 10:57       ` Frederic Weisbecker
2023-09-29 21:09         ` Ingo Molnar
2023-09-29 22:05           ` Frederic Weisbecker
2023-09-29 21:12       ` [tip: timers/core] " tip-bot2 for Ingo Molnar
2023-09-12 10:44 ` [PATCH 3/5] tick/nohz: Don't shutdown the lowres tick from itself Frederic Weisbecker
2023-09-14  1:17   ` Joel Fernandes
2023-09-14  9:29     ` Frederic Weisbecker
2023-09-14 13:26       ` Joel Fernandes
2023-09-27 15:01   ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker
2023-09-12 10:44 ` [PATCH 4/5] tick/nohz: remove unused tick_nohz_idle_stop_tick_protected() Frederic Weisbecker
2023-09-27 15:01   ` [tip: timers/core] tick/nohz: Remove " tip-bot2 for Xueshi Hu
2023-09-12 10:44 ` [PATCH 5/5] timers: Tag (hr)timer softirq as hotplug safe Frederic Weisbecker
2023-09-16  1:38   ` Joel Fernandes
2023-09-18 17:04     ` Thomas Gleixner
2023-09-27 15:01   ` [tip: timers/core] " tip-bot2 for Frederic Weisbecker

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=20230912104406.312185-1-frederic@kernel.org \
    --to=frederic@kernel.org \
    --cc=joel@joelfernandes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vineethrp@gmail.com \
    /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