linux-kernel - Re: Detecting x86 LAPIC timer frequency from CPUID data

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]

Date:   Fri, 19 Apr 2019 22:52:01 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Jacob Pan <jacob.jun.pan@...ux.intel.com>
cc:     Daniel Drake <drake@...lessm.com>, Len Brown <lenb@...nel.org>,
        x86@...nel.org, LKML <linux-kernel@...r.kernel.org>,
        linux@...lessm.com, rjw@...ysocki.net,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: Detecting x86 LAPIC timer frequency from CPUID data

On Fri, 19 Apr 2019, Jacob Pan wrote:
> On Fri, 19 Apr 2019 10:57:10 +0200 (CEST)
> Thomas Gleixner <tglx@...utronix.de> wrote:
> > On Fri, 19 Apr 2019, Daniel Drake wrote:
> > > 0x7FFFFF vs 0x7FFFFFFF, is that intentional?  
> > 
> > I don't think so. Looks like a failed copy and paste. Cc'ed Jacob, he
> > might know.
> > 
> At the time of v2.6.35 both places use 0x7FFFFF. But later this patch
> increased the latter to 0x7FFFFFFF but forgot the first part. So I
> guess it is not exactly a failed copy and paste.
> 
> commit 4aed89d6b515b9185351706ca95cd712c9d8d6a3
> Author: Pierre Tardy <pierre.tardy@...el.com>
> Date:   Thu Jan 6 16:23:29 2011 +0100
> 
>     x86, lapic-timer: Increase the max_delta to 31 bits

Indeed. Thanks for digging that up!

	tglx