From: Tejun Heo <tj@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Leonardo Bras <leobras@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
linux-kernel@vger.kernel.org, Junyao Zhao <junzhao@redhat.com>,
Chris von Recklinghausen <crecklin@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v2 1/1] wq: Avoid using isolated cpus' timers on queue_delayed_work
Date: Fri, 5 Apr 2024 05:38:54 -1000 [thread overview]
Message-ID: <ZhAbDkzlKhvHee49@slm.duckdns.org> (raw)
In-Reply-To: <20240405140449.GB22839@redhat.com>
Hello, Oleg.
On Fri, Apr 05, 2024 at 04:04:49PM +0200, Oleg Nesterov wrote:
...
> > > Don't some archs allow the boot CPU to go down too tho? If so, this doesn't
> > > really solve the problem, right?
> >
> > I do not know. But I thought about this too.
> >
> > In the context of this discussion we do not care if the boot CPU goes down.
> > But we need at least one housekeeping CPU after cpu_down(). The comment in
> > cpu_down_maps_locked() says
> >
> > Also keep at least one housekeeping cpu onlined
> >
> > but it checks HK_TYPE_DOMAIN, and I do not know (and it is too late for me
> > to try to read the code ;) if housekeeping.cpumasks[HK_TYPE_TIMER] can get
> > empty or not.
>
> This nearly killed me, but I managed to convince myself we shouldn't worry
Oh no, don't die. :)
> about cpu_down().
>
> HK_FLAG_TIMER implies HK_FLAG_TICK.
>
> HK_FLAG_TICK implies tick_nohz_full_setup() which sets
> tick_nohz_full_mask = non_housekeeping_mask.
>
> When tick_setup_device() is called on a housekeeping CPU it does
>
> else if (tick_do_timer_boot_cpu != -1 &&
> !tick_nohz_full_cpu(cpu)) {
> tick_take_do_timer_from_boot();
> tick_do_timer_boot_cpu = -1;
>
>
> and this sets tick_do_timer_cpu = first-housekeeping-cpu.
>
> cpu_down(tick_do_timer_cpu) will fail, tick_nohz_cpu_down() will nack it.
>
> So cpu_down() can't make housekeeping.cpumasks[HK_FLAG_TIMER] empty and I
> still think that the change below is the right approach.
>
> But probably WARN_ON() in housekeeping_any_cpu() makes sense anyway.
This would be great.
> What do you think?
>
> Oleg.
>
> > > > So it seems that we should fix housekeeping_setup() ? see the patch below.
> > > >
> > > > In any case the usage of cpu_present_mask doesn't look right to me.
> > > >
> > > > Oleg.
> > > >
> > > > --- a/kernel/sched/isolation.c
> > > > +++ b/kernel/sched/isolation.c
> > > > @@ -129,7 +154,7 @@ static int __init housekeeping_setup(char *str, unsigned long flags)
> > > > cpumask_andnot(housekeeping_staging,
> > > > cpu_possible_mask, non_housekeeping_mask);
> > > >
> > > > - if (!cpumask_intersects(cpu_present_mask, housekeeping_staging)) {
> > > > + if (!cpumask_test_cpu(smp_processor_id(), housekeeping_staging)) {
> > > > __cpumask_set_cpu(smp_processor_id(), housekeeping_staging);
> > > > __cpumask_clear_cpu(smp_processor_id(), non_housekeeping_mask);
> > > > if (!housekeeping.flags) {
Ensuring the boot CPU always be a housekeeping CPU makes sense to me but I'm
not very familiar with the housekeeping code. Frederic, what do you think?
Thanks.
--
tejun
next prev parent reply other threads:[~2024-04-05 15:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 1:00 [PATCH v2 1/1] wq: Avoid using isolated cpus' timers on queue_delayed_work Leonardo Bras
2024-01-30 1:22 ` Tejun Heo
2024-01-30 2:58 ` Leonardo Bras
2024-04-02 10:58 ` Oleg Nesterov
2024-04-03 19:12 ` Tejun Heo
2024-04-03 20:38 ` Oleg Nesterov
2024-04-05 14:04 ` Oleg Nesterov
2024-04-05 15:38 ` Tejun Heo [this message]
2024-04-05 22:03 ` Frederic Weisbecker
2024-04-05 21:52 ` Nohz_full on boot CPU is broken (was: Re: [PATCH v2 1/1] wq: Avoid using isolated cpus' timers on queue_delayed_work) Frederic Weisbecker
2024-04-07 13:09 ` Oleg Nesterov
2024-04-07 13:52 ` Oleg Nesterov
2024-04-09 12:05 ` Frederic Weisbecker
2024-04-09 12:04 ` Frederic Weisbecker
2024-04-09 13:07 ` Oleg Nesterov
2024-04-09 13:59 ` Frederic Weisbecker
2024-04-10 4:26 ` Nicholas Piggin
2024-04-10 13:55 ` Oleg Nesterov
2024-04-11 13:41 ` Oleg Nesterov
2024-04-11 14:39 ` [PATCH] sched/isolation: fix boot crash when the boot CPU is nohz_full Oleg Nesterov
2024-04-11 16:59 ` Oleg Nesterov
2024-04-13 14:17 ` [PATCH] sched/isolation: fix boot crash when maxcpus < first-housekeeping-cpu Oleg Nesterov
2024-04-18 14:54 ` Phil Auld
2024-04-18 15:40 ` Frederic Weisbecker
2024-04-24 20:05 ` [tip: sched/urgent] sched/isolation: Fix boot crash when maxcpus < first housekeeping CPU tip-bot2 for Oleg Nesterov
2024-04-28 8:13 ` Ingo Molnar
2024-04-28 13:16 ` Oleg Nesterov
2024-04-28 8:24 ` tip-bot2 for Oleg Nesterov
2024-04-15 21:37 ` [PATCH] sched/isolation: fix boot crash when the boot CPU is nohz_full Frederic Weisbecker
2024-04-18 14:50 ` Phil Auld
2024-04-22 18:50 ` Oleg Nesterov
2024-04-24 14:42 ` Phil Auld
2024-04-24 20:05 ` [tip: sched/urgent] sched/isolation: {revent " tip-bot2 for Oleg Nesterov
2024-04-24 20:41 ` Phil Auld
2024-04-28 8:14 ` Ingo Molnar
2024-04-29 11:50 ` Phil Auld
2024-04-28 8:24 ` [tip: sched/urgent] sched/isolation: Prevent " tip-bot2 for 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=ZhAbDkzlKhvHee49@slm.duckdns.org \
--to=tj@kernel.org \
--cc=crecklin@redhat.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=junzhao@redhat.com \
--cc=leobras@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).