linux-kernel - Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

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]

Date:   Wed, 26 Apr 2017 10:14:19 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Paolo Bonzini <pbonzini@...hat.com>
Cc:     Satoru Takeuchi <satoru.takeuchi@...il.com>, x86@...nel.org,
        linux-kernel@...r.kernel.org, kvm ML <kvm@...r.kernel.org>
Subject: Re: [BUG] x86: failed to boot a kernel on a Ryzen machine

On Wed, Apr 26, 2017 at 09:48:22AM +0200, Paolo Bonzini wrote:
> The OSXSAVE CPUID bit is not set by QEMU, it is set by the OS itself
> (indirectly) when it sets CR4.OSXSAVE.  QEMU says it's not available
> (probably) because the Opteron_G3 CPU model does not have the 0xD CPUID
> leaf.

Nope:

0x00000000 0x00: eax=0x00000005 ebx=0x68747541 ecx=0x444d4163 edx=0x69746e65
		     ^^^^^^^^^^

highest is 0x5. I'll let Satoru comment on the rest.

Thanks Paolo!

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.