From: Conor Dooley <conor.dooley@microchip.com>
To: Song Shuai <suagrfillet@gmail.com>
Cc: <paul.walmsley@sifive.com>, <palmer@dabbelt.com>,
<aou@eecs.berkeley.edu>, <ajones@ventanamicro.com>,
<sunilvl@ventanamicro.com>, <heiko.stuebner@vrull.eu>,
<apatel@ventanamicro.com>, <evan@rivosinc.com>,
<greentime.hu@sifive.com>, <leyfoon.tan@starfivetech.com>,
<linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] riscv: BUG_ON() for no cpu nodes in setup_smp
Date: Fri, 30 Jun 2023 07:33:55 +0100 [thread overview]
Message-ID: <20230630-tightrope-clatter-6eed9875a76f@wendy> (raw)
In-Reply-To: <0787532c-4520-6d01-c50c-63df207f570c@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2035 bytes --]
Hey,
On Fri, Jun 30, 2023 at 11:02:18AM +0800, Song Shuai wrote:
> 在 2023/6/29 20:33, Conor Dooley 写道:
> > On Thu, Jun 29, 2023 at 06:58:39PM +0800, Song Shuai wrote:
> > > When booting with ACPI tables, the tiny devictree created by
> > > EFI Stub doesn't provide cpu nodes.
> >
>
> "When only the ACPI tables are passed to kernel, the tiny..."
> That seems more accurate. We can use "acpi=" kernel
> parameter to manually enable/disable ACPI.
>
> > What are the conditions that are required to reproduce this issue?
> > When booting with ACPI, why is acpi_disabled true?
> > In my naivety, that seems like a bigger problem to address. >
>
> Actually, I appended the "acpi=off" to kernel cmdline for testing the "off"
> option. That would set acpi_disabled as true.
Yeah, I figured it was intentionally misconfiguration of your kernel,
given that you've tested other niche conditions and reported bugs, just
was not clear from your commit message whether this was a real bugTM
that should be fixed, or some sort of "you booted a kernel that can't be
used on this system".
> > > That's unclear, so bug for no cpu nodes before
> > > of_parse_and_init_cpus().
> >
> > What is unclear? That the reason for the BUG() was that there were no
> > cpu nodes, since it could also be that there were CPU nodes but they
> > were disabled etc?
>
> The BUG() in of_parse_and_init_cpus() indicates there was no boot cpu found
> in the devicetree , not there were no cpu nodes in the devices.
> That's the "unclear" I mean.
Yup, please put that in the commit message so that people don't have to
figure out your intent ;)
> > Or, better yet, move the whole thing into of_parse_and_init_cpus() in
> > the first place? You could drop most of the comment in the process,
> > since I think the details of how you hit this problem would likely not
> > be helpful to anyone that hit it under different conditions.
> ok, I'll apply these comments if you're ok with my replies.
Yup, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-06-30 6:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 10:58 Song Shuai
2023-06-29 12:33 ` Conor Dooley
2023-06-30 3:02 ` Song Shuai
2023-06-30 6:33 ` Conor Dooley [this message]
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=20230630-tightrope-clatter-6eed9875a76f@wendy \
--to=conor.dooley@microchip.com \
--cc=ajones@ventanamicro.com \
--cc=aou@eecs.berkeley.edu \
--cc=apatel@ventanamicro.com \
--cc=evan@rivosinc.com \
--cc=greentime.hu@sifive.com \
--cc=heiko.stuebner@vrull.eu \
--cc=leyfoon.tan@starfivetech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=suagrfillet@gmail.com \
--cc=sunilvl@ventanamicro.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®