[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230124140420.4srnufcvamvff77v@bogus>
Date: Tue, 24 Jan 2023 14:04:20 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Pierre Gondois <pierre.gondois@....com>,
linux-kernel@...r.kernel.org, Palmer Dabbelt <palmer@...osinc.com>,
Sudeep Holla <sudeep.holla@....com>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Len Brown <lenb@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Conor Dooley <conor.dooley@...rochip.com>,
Gavin Shan <gshan@...hat.com>,
linux-arm-kernel@...ts.infradead.org,
linux-riscv@...ts.infradead.org, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v4 6/6] arch_topology: Build cacheinfo from primary CPU
On Tue, Jan 24, 2023 at 02:50:16PM +0100, Geert Uytterhoeven wrote:
> Hi Pierre,
>
[...]
> > @@ -840,6 +840,14 @@ void __init init_cpu_topology(void)
> > reset_cpu_topology();
> > return;
> > }
> > +
> > + for_each_possible_cpu(cpu) {
> > + ret = fetch_cache_info(cpu);
> > + if (ret) {
> > + pr_err("Early cacheinfo failed, ret = %d\n", ret);
>
> This triggers on all my RV64 platforms (K210, Icicle, Starlight,
> RZ/Five).
>
> This seems to be a respin of
> https://lore.kernel.org/all/CAMuHMdUBZ791fxCPkKQ6HCwLE4GJB2S35QC=SQ+X8w5Q4C_70g@mail.gmail.com
> which had the same issue.
>
I need to recollect my memories reading all the thread, but even after the
fixes there were few platforms that failed with so early allocation but were
fine with initcalls. Are these such platforms or am I mixing up things here ?
Do you still see all the cacheinfo in the sysfs with initcalls that happen
later in the boot ?
Conor might help me remember the details.
--
Regards,
Sudeep
Powered by blists - more mailing lists