From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Charalampos Mitrodimas <charmitro@posteo.net>
Cc: Koichiro Den <koichiro.den@canonical.com>,
linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v2] vmstat: disable vmstat_work on vmstat_cpu_down_prep()
Date: Mon, 6 Jan 2025 12:58:31 +0000 [thread overview]
Message-ID: <e0b0fb6e-b00e-4256-98c7-c1c42edd6d97@lucifer.local> (raw)
In-Reply-To: <m2h66ct86n.fsf@posteo.net>
On Mon, Jan 06, 2025 at 12:53:36PM +0000, Charalampos Mitrodimas wrote:
> > I did a bit of printk output and it seems like this _didn't_ online CPU 0,
> > presumably the boot CPU which calls this function in the first instance?
>
> FWIW with the proposed fix I can see that all CPUs are online,
> grep -H . /sys/devices/system/cpu/cpu*/online
> /sys/devices/system/cpu/cpu0/online:1
> /sys/devices/system/cpu/cpu1/online:1
> /sys/devices/system/cpu/cpu2/online:1
> /sys/devices/system/cpu/cpu3/online:1
> /sys/devices/system/cpu/cpu4/online:1
> /sys/devices/system/cpu/cpu5/online:1
> /sys/devices/system/cpu/cpu6/online:1
> /sys/devices/system/cpu/cpu7/online:1
>
Sorry maybe I phrased this badly, I'm not suggesting CPUs aren't coming
online, I'm saying it doesn't look like vmstat_cpu_online() will be called
for the boot CPU, which breaks the proposed fix (the delayed work for this
CPU will simply never be enabled in this case).
Naturally, the boot CPU is _already_ online at this point, which is I
imagine why this is the case.
I had wondered if the function would be invoked on the boot CPU _anyway_
but it appears not.
next prev parent reply other threads:[~2025-01-06 12:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-21 3:33 Koichiro Den
2025-01-03 23:33 ` Lorenzo Stoakes
2025-01-04 4:00 ` Koichiro Den
2025-01-06 2:18 ` Charalampos Mitrodimas
2025-01-06 10:04 ` Mark Rutland
2025-01-06 10:18 ` Geert Uytterhoeven
2025-01-06 10:52 ` Lorenzo Stoakes
2025-01-06 12:53 ` Charalampos Mitrodimas
2025-01-06 12:58 ` Lorenzo Stoakes [this message]
2025-01-06 13:03 ` Koichiro Den
2025-01-06 13:53 ` Koichiro Den
2025-01-07 1:18 ` [PATCH] Simple fix Huacai Chen
2025-01-07 3:35 ` Matthew Wilcox
2025-01-07 3:58 ` Huacai Chen
2025-01-07 8:47 ` Lorenzo Stoakes
2025-01-07 10:29 ` Huacai Chen
2025-01-07 11:00 ` Lorenzo Stoakes
2025-01-08 2:22 ` Koichiro Den
2025-01-08 2:26 ` Koichiro Den
2025-01-08 2:31 ` Huacai Chen
2025-01-08 3:41 ` Koichiro Den
2025-01-08 3:57 ` Huacai Chen
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=e0b0fb6e-b00e-4256-98c7-c1c42edd6d97@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=charmitro@posteo.net \
--cc=koichiro.den@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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