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
| ||
|
Date: Wed, 9 Nov 2022 15:25:44 +0000 From: Sean Christopherson <seanjc@...gle.com> To: Paolo Bonzini <pbonzini@...hat.com> Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org, thomas.lendacky@....com, jmattson@...gle.com, stable@...r.kernel.org Subject: Re: [PATCH 04/11] KVM: SVM: retrieve VMCB from assembly On Wed, Nov 09, 2022, Paolo Bonzini wrote: > Continue moving all accesses to struct vcpu_svm directly in vmenter.S. > This limits the confusion due to different registers used for > argument passing in 32- and 64-bit ABIs. > > It is not strictly necessary for __svm_sev_es_vcpu_run, but staying It's not strictly necessary at all ;-) __svm_sev_es_vcpu_run() > consistent is a good idea since it makes __svm_sev_es_vcpu_run a __svm_sev_es_vcpu_run() > stripped version of _svm_vcpu_run. Missed an underscore. And parantheses. > No functional change intended. > > Cc: stable@...r.kernel.org > Fixes: a149180fbcf3 ("x86: Add magic AMD return-thunk") > Signed-off-by: Paolo Bonzini <pbonzini@...hat.com> > --- Reviewed-by: Sean Christopherson <seanjc@...gle.com>
Powered by blists - more mailing lists