linux-kernel - Re: [RFC] tick_sched_timer() is not properly aligned, fixed by chance

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 for Android: free password hash cracker in your pocket

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

Message-ID: <87mt3lqnde.ffs@tglx>
Date:   Thu, 06 Apr 2023 13:08:29 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Peter Zijlstra <peterz@...radead.org>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:     linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>,
        Pavel Tatashin <pasha.tatashin@...cle.com>
Subject: Re: [RFC] tick_sched_timer() is not properly aligned, fixed by chance

On Thu, Apr 06 2023 at 12:55, Peter Zijlstra wrote:
> On Thu, Apr 06, 2023 at 11:57:35AM +0200, Sebastian Andrzej Siewior wrote:
>
>> The tick_sched_timer story is that it uses ktime_get() to set the
>
> But but but, ktime_get() does not use sched_clock(), it has it's own TSC
> reader.

Correct and at that point during early boot the clocksource which feeds
ktime_get() should be jiffies and not some other random clocksource.

Sebastian, can you please evaluate which clocksource is used for
ktime_get() at the point where the first clock event device is set up?

Thanks,

        tglx