[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <343b8031-f2d7-0d53-6967-d2e5925703cf@microchip.com>
Date: Fri, 15 Jul 2022 14:04:41 +0000
From: <Conor.Dooley@...rochip.com>
To: <sudeep.holla@....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 15/07/2022 10:16, Conor Dooley wrote:
> On 15/07/2022 10:11, Sudeep Holla wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On Thu, Jul 14, 2022 at 04:10:36PM +0000, Conor.Dooley@...rochip.com wrote:
>>> With the GFP_ATOMIC, behaviour is the same as before for me.
>>>
>>
>> So you still get -ENOMEM failure on your platform. It is fine, just that
>> I am bit curious to know why as it succeeds at device_initcall later.
>> I was hoping this might fix your memory allocation failure.
>
> Correct.
I take that back. On today's next with patch 2 applied, I don't see a
problem with no memory, so this does appear to have sorted the memory
allocation failure. Sorry for misleading you & thanks!
With my patches for store_cpu_topology on RISC-V I do see it though,
when called on the boot cpu. I must have mixed up which I had tested.
I have a fix for that though & will update my patches later.
Thanks & apologies!
Conor.
Powered by blists - more mailing lists