linux-kernel - Re: [PATCH 5/7] KVM: SVM: hyper-v: Remote TLB flush for SVM

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: <b3eba256-fb3f-abda-cd83-df0c8f773314@linux.microsoft.com>
Date:   Thu, 8 Apr 2021 09:19:59 -0400
From:   Vineeth Pillai <viremana@...ux.microsoft.com>
To:     Vitaly Kuznetsov <vkuznets@...hat.com>,
        Lan Tianyu <Tianyu.Lan@...rosoft.com>,
        Michael Kelley <mikelley@...rosoft.com>,
        Paolo Bonzini <pbonzini@...hat.com>,
        Sean Christopherson <seanjc@...gle.com>,
        Wanpeng Li <wanpengli@...cent.com>,
        Jim Mattson <jmattson@...gle.com>,
        Joerg Roedel <joro@...tes.org>, Wei Liu <wei.liu@...nel.org>,
        Stephen Hemminger <sthemmin@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>
Cc:     "H. Peter Anvin" <hpa@...or.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
        "K. Y. Srinivasan" <kys@...rosoft.com>, x86@...nel.org,
        kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-hyperv@...r.kernel.org
Subject: Re: [PATCH 5/7] KVM: SVM: hyper-v: Remote TLB flush for SVM


On 4/8/21 7:18 AM, Vitaly Kuznetsov wrote:
>
>>   	enable_gif(svm);
>> @@ -3967,6 +3999,9 @@ static void svm_load_mmu_pgd(struct kvm_vcpu *vcpu, unsigned long root,
>>   		svm->vmcb->control.nested_cr3 = cr3;
>>   		vmcb_mark_dirty(svm->vmcb, VMCB_NPT);
>>   
>> +		if (kvm_x86_ops.tlb_remote_flush)
>> +			kvm_update_arch_tdp_pointer(vcpu->kvm, vcpu, cr3);
>> +
> VMX has "#if IS_ENABLED(CONFIG_HYPERV)" around this, should we add it
> here too?
Agreed. Will fix.

Thanks,
Vineeth