[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220719150513.a525arh663qlhkob@bogus>
Date: Tue, 19 Jul 2022 16:05:13 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Conor Dooley <mail@...chuod.ie>
Cc: Geert Uytterhoeven <geert@...ux-m68k.org>,
Sudeep Holla <sudeep.holla@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Conor Dooley <conor.dooley@...rochip.com>,
valentina.fernandezalanis@...rochip.com,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Qing Wang <wangqing@...o.com>,
Rob Herring <robh+dt@...nel.org>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Ionela Voinescu <ionela.voinescu@....com>,
Pierre Gondois <pierre.gondois@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
linux-riscv <linux-riscv@...ts.infradead.org>,
Gavin Shan <gshan@...hat.com>
Subject: Re: [PATCH v6 09/21] arch_topology: Add support to parse and detect
cache attributes
On Tue, Jul 19, 2022 at 03:37:22PM +0100, Conor Dooley wrote:
> On 19/07/2022 15:22, Geert Uytterhoeven wrote:
> > Hi Sudeep,
> >
>
> Hey Geert,
>
[...]
> >
> > This is triggered
> >
> > Early cacheinfo failed, ret = -12
> >
> > on all my RV64 platforms (K210, PolarFire, StarLight).
>
> This should be fixed by Sudeeps most recent patchset, at least
> it was when I tested it!
> https://lore.kernel.org/all/20220713133344.1201247-1-sudeep.holla@arm.com/
>
Conor you beat me in the response speed :).
> > -12 = -ENOMEM.
> >
> > The boot continues regardless, and the K210 even has enough spare
> > RAM after boot to run "ls", unlike two weeks ago ;-)
> >
Yes Conor initially reported this and I suspected something to do with
per-cpu allocation as the early cacheinfo failed but succeeded in device
initcall level. However when fixing some hotplug issue, I moved the
detection of cache attributes on all cpus from boot cpu to individual
CPUs in the secondary startup which seem to fix the issue as I assume the
per-cpu allocation is ready to use at that stage.
However we still have one pending issue[0] to address even after [1], but
that doesn't affect DT platforms.
--
Regards,
Sudeep
[0] https://lore.kernel.org/all/20220718174151.GA462603@roeck-us.net/
[1] https://lore.kernel.org/all/20220715102609.2160689-1-sudeep.holla@arm.com/
Powered by blists - more mailing lists