linux-kernel - Re: [PATCH v2 2/5] tick/broadcast: Split __tick_broadcast_oneshot

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: <20210527082219.GA21311@willie-the-truck>
Date:   Thu, 27 May 2021 09:22:20 +0100
From:   Will Deacon <will@...nel.org>
To:     Xin Hao <xhao@...ux.alibaba.com>
Cc:     fweisbec@...il.com, john.stultz@...aro.org,
        kernel-team@...roid.com, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org, lorenzo@...gle.com, maz@...nel.org,
        mika.penttila@...tfour.com, sboyd@...nel.org, tglx@...utronix.de
Subject: Re: [PATCH v2 2/5] tick/broadcast: Split
 __tick_broadcast_oneshot_control() into a helper

On Thu, May 27, 2021 at 03:23:06PM +0800, Xin Hao wrote:
>      I  had backport you  tick/broadcast: Prefer per-cpu relatives patches,
> 
> but i did not get the true result,  the Wakeup Devices are all null, why?

Probably because you don't have any suitable per-cpu timers to act as a
wakeup. Do you have a per-cpu timer registered with CLOCK_EVT_FEAT_PERCPU
and CLOCK_EVT_FEAT_ONESHOT but not CLOCK_EVT_FEAT_C3STOP?

Will