From: cruzzhao <cruzzhao@linux.alibaba.com>
To: Aaron Lu <aaron.lu@intel.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, vschneid@redhat.com, paulmck@kernel.org,
quic_neeraju@quicinc.com, joel@joelfernandes.org,
josh@joshtriplett.org, boqun.feng@gmail.com,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
qiang1.zhang@intel.com, jstultz@google.com,
clingutla@codeaurora.org, nsaenzju@redhat.com,
tglx@linutronix.de, frederic@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] sched/core: introduce sched_core_idle_cpu()
Date: Wed, 12 Jul 2023 10:41:11 +0800 [thread overview]
Message-ID: <bac49956-5968-3513-b487-28f99f214967@linux.alibaba.com> (raw)
In-Reply-To: <20230704053946.GA658436@ziqianlu-dell>
在 2023/7/4 下午1:39, Aaron Lu 写道:
>> +#ifdef CONFIG_SCHED_CORE
>> +int sched_core_idle_cpu(int cpu)
>> +{
>> + struct rq *rq = cpu_rq(cpu);
>> +
>> + if (sched_core_enabled(rq) && rq->curr == rq->idle)
>> + return 1;
>
> If the intention is to consider forced idle cpus as idle, then should
> the above condition written as:
>
> if (sched_core_enabled(rq) && rq->core->core_forceidle_count)
> return 1;
> ?
>
> Or as long as a single cookied task is running, all normal idle cpus are
> regarded forced idle here and 1 is returned while previously, idle_cpu()
> is called for those cpus and if they have wakeup task pending, they are
> not regarded as idle so looks like a behaviour change.
>
> Thanks,
> Aaron
>
I'll fix this problem in the next version.
Best,
Cruz Zhao
>> +
>> + return idle_cpu(cpu);
>> +}
>> +
>> +#endif
>> +
>> #ifdef CONFIG_SMP
>> /*
>> * This function computes an effective utilization for the given CPU, to be
>> diff --git a/kernel/softirq.c b/kernel/softirq.c
>> index c8a6913c067d..98b98991ce45 100644
>> --- a/kernel/softirq.c
>> +++ b/kernel/softirq.c
>> @@ -630,7 +630,7 @@ static inline void tick_irq_exit(void)
>> int cpu = smp_processor_id();
>>
>> /* Make sure that timer wheel updates are propagated */
>> - if ((idle_cpu(cpu) && !need_resched()) || tick_nohz_full_cpu(cpu)) {
>> + if ((sched_core_idle_cpu(cpu) && !need_resched()) || tick_nohz_full_cpu(cpu)) {
>> if (!in_hardirq())
>> tick_nohz_irq_exit();
>> }
>> --
>> 2.27.0
>>
next prev parent reply other threads:[~2023-07-12 2:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 4:02 Cruz Zhao
2023-06-29 10:09 ` Frederic Weisbecker
2023-07-03 2:07 ` Joel Fernandes
2023-07-04 5:39 ` Aaron Lu
2023-07-04 13:19 ` Joel Fernandes
2023-07-12 2:41 ` cruzzhao [this message]
2023-07-17 12:56 ` [tip: sched/core] " tip-bot2 for Cruz Zhao
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=bac49956-5968-3513-b487-28f99f214967@linux.alibaba.com \
--to=cruzzhao@linux.alibaba.com \
--cc=aaron.lu@intel.com \
--cc=boqun.feng@gmail.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=clingutla@codeaurora.org \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jiangshanlai@gmail.com \
--cc=jirislaby@kernel.org \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=nsaenzju@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qiang1.zhang@intel.com \
--cc=quic_neeraju@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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®