mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zhongqiu Han <zhongqiu.han@oss.qualcomm.com>
To: Zhan Xusheng <zhanxusheng1024@gmail.com>, thnkslprpt@gmail.com
Cc: rafael@kernel.org, viresh.kumar@linaro.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	zhanxusheng@xiaomi.com, zhongqiu.han@oss.qualcomm.com
Subject: Re: [PATCH] cpufreq: schedutil: Skip busy-CPU hold when NOHZ is disabled
Date: Tue, 3 Nov 2026 19:03:29 +0800	[thread overview]
Message-ID: <78af4d6d-7465-4980-9d8b-e832db76a08e@oss.qualcomm.com> (raw)
In-Reply-To: <20261103071729.1556217-1-zhanxusheng1024@gmail.com>

On 11/3/2026 3:17 PM, Zhan Xusheng wrote:
> Hi Avi,
> 
> On Tue, Nov 03, 2026 at 08:15:57AM +0200, Avi Weiss wrote:
>> +	if (!tick_nohz_enabled)
>> +		return false;
> 
> idle_calls also never moves when nohz is enabled but was never
> activated, because tick_check_oneshot_change() found no oneshot clock
> event device or no clocksource valid for high resolution. TS_FLAG_NOHZ
> then stays clear, as with nohz=off. tick_nohz_is_active() covers both:
> 
> 	if (!tick_nohz_is_active())
> 		return false;

Agree with Xusheng, tick_nohz_is_active() is one more reasonable check,
it also covers NOHZ never getting activated. Besides please Cc: stable,
and Cc the scheduler maintainers (scripts/get_maintainer.pl).

Note that this still leaves the nohz_full timekeeping CPU and idle=poll,
where NOHZ is active but idle_calls never moves either. That's a deeper
issue with using a tick-stop counter as an "idle recently" signal and
it may be addressed separately.

> 
> Thanks,
> Zhan Xusheng
> 


-- 
Thx and BRs,
Zhongqiu Han

      reply	other threads:[~2026-11-03 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03  6:15 Avi Weiss
2026-11-03  7:17 ` Zhan Xusheng
2026-11-03 11:03   ` Zhongqiu Han [this message]

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=78af4d6d-7465-4980-9d8b-e832db76a08e@oss.qualcomm.com \
    --to=zhongqiu.han@oss.qualcomm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=thnkslprpt@gmail.com \
    --cc=viresh.kumar@linaro.org \
    --cc=zhanxusheng1024@gmail.com \
    --cc=zhanxusheng@xiaomi.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

all inboxes | Powered by JetHome®