linux-kernel - Re: [PATCH 00/14] KVM: x86: Make Hyper-V emulation optional

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, 29 Nov 2023 17:42:04 -0800
From:   Sean Christopherson <seanjc@...gle.com>
To:     Vitaly Kuznetsov <vkuznets@...hat.com>
Cc:     kvm@...r.kernel.org, Paolo Bonzini <pbonzini@...hat.com>,
        Maxim Levitsky <mlevitsk@...hat.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/14] KVM: x86: Make Hyper-V emulation optional

On Wed, Oct 25, 2023, Vitaly Kuznetsov wrote:
> Vitaly Kuznetsov (14):
>   KVM: x86: xen: Remove unneeded xen context from struct kvm_arch when
>     !CONFIG_KVM_XEN
>   KVM: x86: hyper-v: Move Hyper-V partition assist page out of Hyper-V
>     emulation context
>   KVM: VMX: Split off vmx_onhyperv.{ch} from hyperv.{ch}
>   KVM: x86: hyper-v: Introduce kvm_hv_synic_auto_eoi_set()
>   KVM: x86: hyper-v: Introduce kvm_hv_synic_has_vector()
>   KVM: VMX: Split off hyperv_evmcs.{ch}
>   KVM: x86: hyper-v: Introduce kvm_hv_nested_transtion_tlb_flush()
>     helper
>   KVM: selftests: Make all Hyper-V tests explicitly dependent on Hyper-V
>     emulation support in KVM
>   KVM: selftests: Fix vmxon_pa == vmcs12_pa == -1ull
>     vmx_set_nested_state_test for !eVMCS case
>   KVM: x86: Make Hyper-V emulation optional
>   KVM: nVMX: hyper-v: Introduce nested_vmx_evmptr12() and
>     nested_vmx_is_evmptr12_valid() helpers
>   KVM: nVMX: hyper-v: Introduce nested_vmx_evmcs() accessor
>   KVM: nVMX: hyper-v: Hide more stuff under CONFIG_KVM_HYPERV
>   KVM: nSVM: hyper-v: Hide more stuff under
>     CONFIG_KVM_HYPERV/CONFIG_HYPERV

No major complaints.  If it hadn't been for the build failure, I likely wouldn't
have even bothered with most of my nits ;-)

I'll wait for v2 though, trying to fixup as I go will be a bit risky.