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:   Sun, 7 Feb 2021 14:31:28 -0800
From:   Dave Hansen <>
To:     "Kirill A. Shutemov" <>
Cc:     Andy Lutomirski <>,
        Kuppuswamy Sathyanarayanan 
        Peter Zijlstra <>,
        Andi Kleen <>,
        Kirill Shutemov <>,
        Kuppuswamy Sathyanarayanan <>,
        Dan Williams <>,
        Raj Ashok <>,
        Sean Christopherson <>,
        LKML <>
Subject: Re: [RFC v1 09/26] x86/tdx: Handle CPUID via #VE

On 2/7/21 12:29 PM, Kirill A. Shutemov wrote:
>> Couldn't you just have one big helper that takes *all* the registers
>> that get used in any TDVMCALL and sets all the rcx bits?  The users
>> could just pass 0's for the things they don't use.
>> Then you've got the ugly inline asm in one place.  It also makes it
>> harder to screw up the 'rcx' mask and end up passing registers you
>> didn't want into a malicious VMM.
> For now we only pass down R10-R15, but the interface allows to pass down
> much wider set of registers, including XMM. How far do we want to get it?

Just do what we immediately need: R10-R15.

Powered by blists - more mailing lists