From: Frederic Weisbecker <frederic@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tick: shift tick_nohz_switch_to_nohz() from tick_check_oneshot_change() to hrtimer_run_queues()
Date: Thu, 30 May 2024 17:24:56 +0200 [thread overview]
Message-ID: <ZliaSISeFxx_FQ6O@localhost.localdomain> (raw)
In-Reply-To: <20240530124203.GA26990@redhat.com>
Le Thu, May 30, 2024 at 02:42:03PM +0200, Oleg Nesterov a écrit :
> hrtimer_run_queues() calls tick_check_oneshot_change() to check if we
> can switch to highres or nohz mode, but the current code looks very
> confusing to me. In the highres=n or CONFIG_HIGH_RES_TIMERS=n cases
> tick_check_oneshot_change() itself calls tick_nohz_switch_to_nohz()
> and returns zero; that is why it needs the "allow_nohz" argument,
> which imo also adds confusion.
>
> This patch turns tick_check_oneshot_change() into a "pure" function
> without arguments. hrtimer_run_queues() calls hrtimer_switch_to_hres()
> or tick_nohz_switch_to_nohz() depending on hrtimer_is_hres_enabled().
>
> Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> ---
> kernel/time/hrtimer.c | 7 +++++--
> kernel/time/tick-internal.h | 6 ++++--
> kernel/time/tick-sched.c | 15 ++++-----------
> 3 files changed, 13 insertions(+), 15 deletions(-)
>
> diff --git a/kernel/time/hrtimer.c b/kernel/time/hrtimer.c
> index 492c14aac642..806f352b095d 100644
> --- a/kernel/time/hrtimer.c
> +++ b/kernel/time/hrtimer.c
> @@ -1891,8 +1891,11 @@ void hrtimer_run_queues(void)
> * there only sets the check bit in the tick_oneshot code,
> * otherwise we might deadlock vs. xtime_lock.
> */
> - if (tick_check_oneshot_change(!hrtimer_is_hres_enabled())) {
> - hrtimer_switch_to_hres();
> + if (tick_check_oneshot_change()) {
> + if (hrtimer_is_hres_enabled())
> + hrtimer_switch_to_hres();
> + else
> + tick_nohz_switch_to_nohz();
Thanks a lot for clarifying this! I've always found that confusing
(and note how I never did anything about it!)
Just a detail below:
> return;
> }
>
> diff --git a/kernel/time/tick-internal.h b/kernel/time/tick-internal.h
> index 5f2105e637bd..6764fbd18afd 100644
> --- a/kernel/time/tick-internal.h
> +++ b/kernel/time/tick-internal.h
> @@ -111,7 +111,8 @@ extern void tick_resume_oneshot(void);
> static inline bool tick_oneshot_possible(void) { return true; }
> extern int tick_oneshot_mode_active(void);
> extern void tick_clock_notify(void);
> -extern int tick_check_oneshot_change(int allow_nohz);
> +extern int tick_check_oneshot_change(void);
> +extern void tick_nohz_switch_to_nohz(void);
tick_nohz_switch_to_nohz() is only built with CONFIG_NO_HZ_COMMON
You will have a build issue with CONFIG_HIGH_RES_TIMER && !CONFIG_NO_HZ_COMMON
> extern int tick_init_highres(void);
> #else /* !CONFIG_TICK_ONESHOT: */
> static inline
> @@ -124,7 +125,8 @@ static inline void tick_oneshot_notify(void) { }
> static inline bool tick_oneshot_possible(void) { return false; }
> static inline int tick_oneshot_mode_active(void) { return 0; }
> static inline void tick_clock_notify(void) { }
> -static inline int tick_check_oneshot_change(int allow_nohz) { return 0; }
> +static inline int tick_check_oneshot_change(void) { return 0; }
> +static inline void tick_nohz_switch_to_nohz(void) { }
> #endif /* !CONFIG_TICK_ONESHOT */
next prev parent reply other threads:[~2024-05-30 15:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 12:42 [PATCH] tick: shift tick_nohz_switch_to_nohz() from tick_check_oneshot_change() to hrtimer_run_queues() Oleg Nesterov
2024-05-30 15:24 ` Frederic Weisbecker [this message]
2024-05-30 17:12 ` Oleg Nesterov
2024-06-01 14:56 ` Oleg Nesterov
2024-05-31 0:28 ` kernel test robot
2024-05-31 1:21 ` kernel test robot
2024-06-02 10:20 ` [PATCH v2] " Oleg Nesterov
2024-06-03 8:14 ` Thomas Gleixner
2024-06-03 13:41 ` Oleg Nesterov
2024-06-03 15:03 ` Oleg Nesterov
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=ZliaSISeFxx_FQ6O@localhost.localdomain \
--to=frederic@kernel.org \
--cc=anna-maria@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
/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