From: Palmer Dabbelt <palmer@dabbelt.com>
To: kernelfans@gmail.com
Cc: linux-riscv@lists.infradead.org, kernelfans@gmail.com,
Paul Walmsley <paul.walmsley@sifive.com>,
aou@eecs.berkeley.edu, jszhang@kernel.org
Subject: Re: [PATCH] riscv: cpu-hotplug: clear cpu from numa map when teardown
Date: Tue, 08 Feb 2022 17:13:21 -0800 (PST) [thread overview]
Message-ID: <mhng-9439ea0d-b7ab-48ed-a359-702383ad6321@palmer-ri-x1c9> (raw)
In-Reply-To: <20220123121352.13199-1-kernelfans@gmail.com>
On Sun, 23 Jan 2022 04:13:52 PST (-0800), kernelfans@gmail.com wrote:
> There is numa_add_cpu() when cpus online, accordingly, there should be
> numa_remove_cpu() when cpus offline.
>
> Signed-off-by: Pingfan Liu <kernelfans@gmail.com>
> Cc: Paul Walmsley <paul.walmsley@sifive.com>
> Cc: Palmer Dabbelt <palmer@dabbelt.com>
> Cc: Albert Ou <aou@eecs.berkeley.edu>
> Cc: Jisheng Zhang <jszhang@kernel.org>
> To: linux-riscv@lists.infradead.org
> ---
> arch/riscv/kernel/cpu-hotplug.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/riscv/kernel/cpu-hotplug.c b/arch/riscv/kernel/cpu-hotplug.c
> index be7f05b542bb..78d156a359ef 100644
> --- a/arch/riscv/kernel/cpu-hotplug.c
> +++ b/arch/riscv/kernel/cpu-hotplug.c
> @@ -40,6 +40,7 @@ int __cpu_disable(void)
> return ret;
>
> remove_cpu_topology(cpu);
> + numa_remove_cpu(cpu);
> set_cpu_online(cpu, false);
> irq_migrate_all_off_this_cpu();
Thanks, this is on fixes. I don't really have any NUMA-related test
setups, but if someone has a QEMU-based config that's meaningful then
I'm happy to add it.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-02-09 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 12:13 [PATCH] riscv: cpu-hotplug: clear cpu from numa map when teardown Pingfan Liu
2022-02-09 1:13 ` Palmer Dabbelt [this message]
2022-02-09 7:36 ` Pingfan Liu
2022-02-10 17:45 ` Palmer Dabbelt
2022-02-10 19:35 ` Atish Patra
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=mhng-9439ea0d-b7ab-48ed-a359-702383ad6321@palmer-ri-x1c9 \
--to=palmer@dabbelt.com \
--cc=aou@eecs.berkeley.edu \
--cc=jszhang@kernel.org \
--cc=kernelfans@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=paul.walmsley@sifive.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.