[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220714160016.honjpzg35ccq4fto@bogus>
Date: Thu, 14 Jul 2022 17:00:16 +0100
From: Sudeep Holla <sudeep.holla@....com>
To: Conor.Dooley@...rochip.com
Cc: linux-kernel@...r.kernel.org, gregkh@...uxfoundation.org,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
ionela.voinescu@....com, pierre.gondois@....com,
linux-arm-kernel@...ts.infradead.org,
linux-riscv@...ts.infradead.org
Subject: Re: [PATCH -next] arch_topology: Fix cache attributes detection in
the CPU hotplug path
On Thu, Jul 14, 2022 at 03:27:09PM +0000, Conor.Dooley@...rochip.com wrote:
> On 14/07/2022 16:01, Sudeep Holla wrote:
> >
> > Interesting, need to check if it is not in atomic context on arm64.
> > Wonder if some configs are disabled and making this bug hidden. Let me
> > check.
> >
OK, it turns I didn't have necessary config options enabled. Enabling
them, I did see the BUG splat and changing allocation to GFP_ATOMIC
fixed the same. Can you try that please so that you can test if other
things are fine.
> > One possible solution is to add GFP_ATOMIC to the allocation but I want
> > to make sure if it is legal to be in atomic context when calling
> > update_siblings_masks.
> >
So I take is as legal and needs to be fixed to push my patch.
> >>>
> >>> Anyways give this a try, also test the CPU hotplug and check if nothing
> >>> is broken on RISC-V. We noticed this bug only on one platform while
> >>
> >> So, our system monitor that runs openSBI does not actually support
> >> any hotplug features yet, so:
> >
> > OK, we can ignore hotplug on RISC-V for now then. We have tested on multiple
> > arm64 platforms(DT as well as ACPI).
> >
>
> Well, other vendors implementations of firmware-come-bootloaders-
> running-openSBI may support it, but (currently) ours does not.
> But, if no-one else is speaking up about this, my arch-topo changes
> or your original patchset...
OK
--
Regards,
Sudeep
Powered by blists - more mailing lists