linux-kernel - RE: [PATCH 2/4] x86/mce: Get rid of machine_check

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: <d090a19ce8f74b0ea557f180d185df3e@intel.com>
Date:   Mon, 20 Sep 2021 16:04:35 +0000
From:   "Luck, Tony" <tony.luck@...el.com>
To:     Borislav Petkov <bp@...en8.de>
CC:     Yazen Ghannam <Yazen.Ghannam@....com>, X86 ML <x86@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 2/4] x86/mce: Get rid of machine_check_vector

> It is there to tell you how many bits you have left so that you don't
> have to count each time. And updating it each time is simply Ctrl-x in
> vim.

You want to know how many bit are left for some reason?  Is there some
user API that will break if we overflow and start allocating bits from the next
64-bit word? Or is this just the countdown for when you and I both have a nervous
breakdown trying to keep track of that many different option paths through the
machine check code :-)

Thanks for the tip about Ctrl-x to decrement a number in vim (Google
tell me Ctrl-a increments). Learned something new today :-)

-Tony