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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 Dec 2020 11:16:56 +0100 From: Paolo Bonzini <pbonzini@...hat.com> To: Sean Christopherson <seanjc@...gle.com>, Tom Lendacky <thomas.lendacky@....com> Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, x86@...nel.org, Jim Mattson <jmattson@...gle.com>, Joerg Roedel <joro@...tes.org>, Vitaly Kuznetsov <vkuznets@...hat.com>, Wanpeng Li <wanpengli@...cent.com>, Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, Brijesh Singh <brijesh.singh@....com> Subject: Re: [PATCH v5 12/34] KVM: SVM: Add initial support for a VMGEXIT VMEXIT On 14/12/20 20:41, Sean Christopherson wrote: > I agree VMGEXIT should be added to the hot path, it could very well be the most > common exit reason due to all instruction-based emulation getting funneled > through VMGEXIT. Yeah, I was thinking that not many guests will be SEV-ES. On the other hand, it's quite likely to have an SEV-ES guest in your hands once the really common non-VMGEXITs have been eliminated. Paolo
Powered by blists - more mailing lists