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: <797B7A87-AAFB-4302-96E6-3FD956D614C2@zytor.com>
Date: Thu, 08 May 2025 13:40:45 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Andrew Cooper <andrew.cooper3@...rix.com>,
        "Ahmed S. Darwish" <darwi@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        Dave Hansen <dave.hansen@...ux.intel.com>
CC: Thomas Gleixner <tglx@...utronix.de>,
        John Ogness <john.ogness@...utronix.de>, x86@...nel.org,
        x86-cpuid@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 02/26] x86/cpu: Sanitize CPUID(0x80000000) output

On May 7, 2025 1:50:48 AM PDT, Andrew Cooper <andrew.cooper3@...rix.com> wrote:
>On 06/05/2025 6:04 am, Ahmed S. Darwish wrote:
>> CPUID(0x80000000).EAX returns the max extended CPUID leaf available.  On
>> x86-32 machines
>
>How certain are you that it's all 32bit CPUs?  AIUI, it's an Intel
>specific behaviour, not shared by other x86 vendors of the same era.
>
>~Andrew

All 64-bit machines require CPUID leaf 0x80000000.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ