From: Francesco Lavra <francescolavra.fl@gmail.com>
To: seanjc@google.com
Cc: airlied@gmail.com, bp@alien8.de, dave.hansen@linux.intel.com,
dri-devel@lists.freedesktop.org, kai.huang@intel.com,
kevinloughlin@google.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, maarten.lankhorst@linux.intel.com,
mingo@redhat.com, mizhang@google.com, mripard@kernel.org,
pbonzini@redhat.com, simona@ffwll.ch, szy0127@sjtu.edu.cn,
tglx@linutronix.de, thomas.lendacky@amd.com,
tzimmermann@suse.de, x86@kernel.org
Subject: Re: [PATCH v2 5/8] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency
Date: Sun, 18 May 2025 11:52:07 +0200 [thread overview]
Message-ID: <4fde4c953a4204e70d89f2c3dfd24eccdac0540f.camel@gmail.com> (raw)
In-Reply-To: <20250516212833.2544737-6-seanjc@google.com>
On 2025-05-16 at 21:28, Sean Christopherson wrote:
> @@ -3901,7 +3908,7 @@ void sev_snp_init_protected_guest_state(struct
> kvm_vcpu *vcpu)
> * From this point forward, the VMSA will always be a guest-
> mapped page
> * rather than the initial one allocated by KVM in svm-
> >sev_es.vmsa. In
> * theory, svm->sev_es.vmsa could be free'd and cleaned up here,
> but
> - * that involves cleanups like wbinvd_on_all_cpus() which would
> ideally
> + * that involves cleanups like flushing caches, which would
> ideally be
> * be handled during teardown rather than guest boot. Deferring
> that
Duplicate "be"
next prev parent reply other threads:[~2025-05-18 9:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 21:28 [PATCH v2 0/8] x86, KVM: Optimize SEV cache flushing Sean Christopherson
2025-05-16 21:28 ` [PATCH v2 1/8] KVM: SVM: Remove wbinvd in sev_vm_destroy() Sean Christopherson
2025-05-16 21:28 ` [PATCH v2 2/8] drm/gpu: Remove dead checks on wbinvd_on_all_cpus()'s return value Sean Christopherson
2025-05-16 21:28 ` [PATCH v2 3/8] x86, lib: Drop the unused return value from wbinvd_on_all_cpus() Sean Christopherson
2025-05-17 6:47 ` Ingo Molnar
2025-05-16 21:28 ` [PATCH v2 4/8] x86, lib: Add WBNOINVD helper functions Sean Christopherson
2025-05-17 6:47 ` Ingo Molnar
2025-05-19 16:30 ` Sean Christopherson
2025-05-20 9:41 ` Ingo Molnar
2025-05-16 21:28 ` [PATCH v2 5/8] KVM: SEV: Prefer WBNOINVD over WBINVD for cache maintenance efficiency Sean Christopherson
2025-05-18 9:52 ` Francesco Lavra [this message]
2025-05-16 21:28 ` [PATCH v2 6/8] KVM: x86: Use wbinvd_on_cpu() instead of an open-coded equivalent Sean Christopherson
2025-05-16 21:28 ` [PATCH v2 7/8] x86, lib: Add wbinvd and wbnoinvd helpers to target multiple CPUs Sean Christopherson
2025-05-17 7:01 ` Ingo Molnar
2025-05-19 16:02 ` Sean Christopherson
2025-05-19 16:34 ` Sean Christopherson
2025-05-20 9:42 ` Ingo Molnar
2025-05-16 21:28 ` [PATCH v2 8/8] KVM: SVM: Flush cache only on CPUs running SEV guest Sean Christopherson
2025-05-19 17:48 ` Tom Lendacky
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=4fde4c953a4204e70d89f2c3dfd24eccdac0540f.camel@gmail.com \
--to=francescolavra.fl@gmail.com \
--cc=airlied@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kai.huang@intel.com \
--cc=kevinloughlin@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mingo@redhat.com \
--cc=mizhang@google.com \
--cc=mripard@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=simona@ffwll.ch \
--cc=szy0127@sjtu.edu.cn \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tzimmermann@suse.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.