linux-kernel - Re: [PATCH v4 2/8] timers/migration: Move hierarchy setup into cpuhotplug prepare callback

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dfe34cb9-1a71-4f3b-ae71-52e886d11768@nvidia.com>
Date: Mon, 15 Jul 2024 14:25:46 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Frederic Weisbecker <frederic@...nel.org>
Cc: Alexander Stein <alexander.stein@...tq-group.com>,
 Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
 Anna-Maria Behnsen <anna-maria@...utronix.de>,
 "linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH v4 2/8] timers/migration: Move hierarchy setup into
 cpuhotplug prepare callback


On 15/07/2024 11:44, Frederic Weisbecker wrote:
> Hi,
> 
> Le Mon, Jul 15, 2024 at 11:39:40AM +0100, Jon Hunter a écrit :
>>
>> On 11/07/2024 09:56, Alexander Stein wrote:
>>> Hi,
>>>
>>> Am Mittwoch, 3. Juli 2024, 22:28:39 CEST schrieb Anna-Maria Behnsen:
>>>> When a CPU comes online the first time, it is possible that a new top level
>>>> group will be created. In general all propagation is done from the bottom
>>>> to top. This minimizes complexity and prevents possible races. But when a
>>>> new top level group is created, the formely top level group needs to be
>>>> connected to the new level. This is the only time, when the direction to
>>>> propagate changes is changed: the changes are propagated from top (new top
>>>> level group) to bottom (formerly top level group).
>>>
>>> Now that this commit is integrated in linux-next I'm starting to see the
>>> kernel error message:
>>>> Timer migration setup failed
>>> on my arm64 i.MX8MP platform (imx8mp-tqma8mpql-mba8mpxl.dts).
>>
>>
>> I am also seeing the same on our 32-bit and 64-bit ARM Tegra boards.
>>
>> Any feedback on this?
> 
> The patches have been reverted on -tip (still in -next?) and Anna-Maria is
> working on a new version.


Thanks! They were in next-20240715 looking at this mornings tests.

Jon

-- 
nvpublic