From: Tom Lendacky <thomas.lendacky@amd.com>
To: Zheyun Shen <szy0127@sjtu.edu.cn>,
Sean Christopherson <seanjc@google.com>,
pbonzini <pbonzini@redhat.com>, tglx <tglx@linutronix.de>
Cc: kvm <kvm@vger.kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] KVM:SVM: Flush cache only on CPUs running SEV guest
Date: Wed, 13 Mar 2024 09:32:06 -0500 [thread overview]
Message-ID: <fd2a75f0-4baa-4d2b-b350-4f38da32c670@amd.com> (raw)
In-Reply-To: <90e5bdac-3b13-41bd-b1c1-981c35891f34@amd.com>
On 3/12/24 09:45, Tom Lendacky wrote:
> On 3/6/24 20:14, Zheyun Shen wrote:
>> On AMD CPUs without ensuring cache consistency, each memory page
>> reclamation in an SEV guest triggers a call to wbinvd_on_all_cpus(),
>> thereby affecting the performance of other programs on the host.
>>
>> Typically, an AMD server may have 128 cores or more, while the SEV guest
>> might only utilize 8 of these cores. Meanwhile, host can use qemu-affinity
>> to bind these 8 vCPUs to specific physical CPUs.
>>
>> Therefore, keeping a record of the physical core numbers each time a vCPU
>> runs can help avoid flushing the cache for all CPUs every time.
>>
>> Since the usage of sev_flush_asids() isn't tied to a single VM, we just
>> replace all wbinvd_on_all_cpus() with sev_do_wbinvd() except for that
>> in sev_flush_asids().
>>
>> Signed-off-by: Zheyun Shen <szy0127@sjtu.edu.cn>
>
> I'm unable to launch my SEV or SEV-ES guests with this patch (haven't
> tried an SEV-SNP guest, yet). Qemu segfaults at launch.
>
> I'll try to dig into what is happening, but not sure when I'll be able to
> do that at the moment.
Looks like it's the use of get_cpu() without an associated put_cpu() when
setting the cpumask. I think what you really want to use is just the cpu
parameter that is passed into pre_sev_run().
>
>> void sev_free_vcpu(struct kvm_vcpu *vcpu)
>> @@ -2648,6 +2666,7 @@ void pre_sev_run(struct vcpu_svm *svm, int cpu)
>> sd->sev_vmcbs[asid] = svm->vmcb;
>> svm->vmcb->control.tlb_ctl = TLB_CONTROL_FLUSH_ASID;
>> vmcb_mark_dirty(svm->vmcb, VMCB_ASID);
>> + cpumask_set_cpu(get_cpu(), sev_get_wbinvd_dirty_mask(svm->vcpu.kvm));
Just use 'cpu' here.... ^
When I do that I'm able to boot an SEV and SEV-ES guest.
I'll wait for the next version, in case there are other changes, before
running through our CI for more thorough testing than just a single boot.
Thanks,
Tom
>> }
>> #define GHCB_SCRATCH_AREA_LIMIT (16ULL * PAGE_SIZE)
prev parent reply other threads:[~2024-03-13 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 2:14 Zheyun Shen
2024-03-12 14:45 ` Tom Lendacky
2024-03-13 14:32 ` Tom Lendacky [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd2a75f0-4baa-4d2b-b350-4f38da32c670@amd.com \
--to=thomas.lendacky@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=szy0127@sjtu.edu.cn \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®