From: Michael Ellerman <mpe@ellerman.id.au>
To: Pingfan Liu <kernelfans@gmail.com>,
Pingfan Liu <piliu@redhat.com>,
Hari Bathini <hbathini@linux.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH 5/5] powerpc/smp: Remap boot CPU onto core 0 if >= nr_cpu_ids
Date: Fri, 29 Dec 2023 23:07:45 +1100 [thread overview]
Message-ID: <87tto1jjou.fsf@mail.lhotse> (raw)
In-Reply-To: <20231229120107.2281153-5-mpe@ellerman.id.au>
Michael Ellerman <mpe@ellerman.id.au> writes:
> If nr_cpu_ids is too low to include the boot CPU, remap the boot CPU
> onto logical core 0.
Hi guys,
I finally got time to look at this issue. I think this series should fix
the problems that have been seen. I've tested this fairly thoroughly
with a qemu script, and also a few boots on a real machine.
If you can test it with your setups that would be great. Hopefully there
isn't some obscure case I've missed.
cheers
next prev parent reply other threads:[~2023-12-29 12:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 12:01 [RFC PATCH 1/5] powerpc/smp: Adjust nr_cpu_ids to cover all threads of a core Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 2/5] powerpc/smp: Increase nr_cpu_ids to include the boot CPU Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 3/5] powerpc/smp: Lookup avail once per device tree node Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 4/5] powerpc/smp: Factor out assign_threads() Michael Ellerman
2024-01-02 4:34 ` Aneesh Kumar K.V
2024-02-14 13:10 ` Michael Ellerman
2023-12-29 12:01 ` [RFC PATCH 5/5] powerpc/smp: Remap boot CPU onto core 0 if >= nr_cpu_ids Michael Ellerman
2023-12-29 12:07 ` Michael Ellerman [this message]
2024-01-02 0:51 ` Pingfan Liu
2024-02-13 20:16 ` Wen Xiong
2024-01-02 4:46 ` Aneesh Kumar K.V
2024-02-09 15:56 ` Jiri Bohac
2024-02-14 13:12 ` Michael Ellerman
2024-02-15 13:00 ` [RFC PATCH 1/5] powerpc/smp: Adjust nr_cpu_ids to cover all threads of a core Michael Ellerman
2024-02-16 2:42 ` Pingfan Liu
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=87tto1jjou.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=hbathini@linux.ibm.com \
--cc=kernelfans@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=piliu@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 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.