linux-kernel - Re: [GIT pull] x86/timers updates for 4.13

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: <CA+55aFyXwVqZbdgPf4gpA3ArxRpMyqKSxH40td=vUhLNh813fw@mail.gmail.com>
Date:   Mon, 3 Jul 2017 18:06:02 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Ingo Molnar <mingo@...nel.org>,
        "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [GIT pull] x86/timers updates for 4.13

On Mon, Jul 3, 2017 at 1:20 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
>
> This update contains:
>
>    - The final solution for the TSC deadline timer borkage, which is caused
>      by a hardware problem in the TSC_ADJUST/TSC_DEADLINE_TIMER logic.
>
>      The problem is documented now fixed with a microcode update, so we can
>      remove the workaround and check for the microcode version. If the
>      microcode is not up to date, then the TSC deadline timer is
>      enabled. If the borkage is fixed by the proper micro code version,
>      then the deadline timer can be used. In both cases the restrictions to
>      the range of the TSC_ADJUST value, which were added as workarounds,
>      are removed.
>
>   - A few simple fixes and updates to the timer related x86 code.

That deadline timer explanation made no sense.

I edited it to what I think you wanted to say in the commit message.

               Linus