linux-kernel - Re: [PATCH v2] KVM: nVMX: Sync L2 guest CET states between L1/L2

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: <39737fcf-ac15-006e-c21f-39f6caa3b342@redhat.com>
Date:   Tue, 2 Mar 2021 10:33:59 +0100
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Yang Weijiang <weijiang.yang@...el.com>,
        Sean Christopherson <seanjc@...gle.com>
Cc:     kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        Vitaly Kuznetsov <vkuznets@...hat.com>
Subject: Re: [PATCH v2] KVM: nVMX: Sync L2 guest CET states between L1/L2

On 02/03/21 10:05, Yang Weijiang wrote:
> I got some description from MSFT as below, do you mean that:
> 
> GuestSsp uses clean field GUEST_BASIC (bit 10)
> GuestSCet/GuestInterruptSspTableAddr uses GUEST_GRP1 (bit 11)
> HostSCet/HostSsp/HostInterruptSspTableAddr uses HOST_GRP1 (bit 14)
> 
> If it is, should these go into separate patch series for Hyper-v nested
> support? I have some pending patches for the enabling.

Yes, it should be a separate patch.  The main patch however should add 
the CET fields to EVMCS1_UNSUPPORTED_VMENTRY_CTRL and 
EVMCS1_UNSUPPORTED_VMEXIT_CTRL.

Thanks,

Paolo