From: Sean Christopherson <seanjc@google.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Zheyun Shen <szy0127@sjtu.edu.cn>,
pbonzini@redhat.com, tglx@linutronix.de,
kevinloughlin@google.com, mingo@redhat.com, bp@alien8.de,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/3] KVM: x86: Add a wbinvd helper
Date: Tue, 25 Feb 2025 16:59:52 -0800 [thread overview]
Message-ID: <Z75niMjZTQQ28HKP@google.com> (raw)
In-Reply-To: <5fb9fa5e-5769-3ad8-32d8-e4a045f041a1@amd.com>
On Thu, Feb 06, 2025, Tom Lendacky wrote:
> On 1/27/25 19:53, Zheyun Shen wrote:
> > At the moment open-coded calls to on_each_cpu_mask() are used when
> > emulating wbinvd. A subsequent patch needs the same behavior and the
> > helper prevents callers from preparing some idential parameters.
> >
> > Signed-off-by: Zheyun Shen <szy0127@sjtu.edu.cn>
>
> Not sure if this wouldn't be better living in the same files that
> wbinvd_on_all_cpus() lives, so I'll leave it up to the maintainers.
It definitely belongs in arch/x86/lib/cache-smp.c.
next prev parent reply other threads:[~2025-02-26 0:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 1:53 [PATCH v7 0/3] KVM: SVM: Flush cache only on CPUs running SEV guest Zheyun Shen
2025-01-28 1:53 ` [PATCH v7 1/3] KVM: x86: Add a wbinvd helper Zheyun Shen
2025-02-06 22:03 ` Tom Lendacky
2025-02-26 0:59 ` Sean Christopherson [this message]
2025-01-28 1:53 ` [PATCH v7 2/3] KVM: SVM: Remove wbinvd in sev_vm_destroy() Zheyun Shen
2025-02-06 22:04 ` Tom Lendacky
2025-01-28 1:53 ` [PATCH v7 3/3] KVM: SVM: Flush cache only on CPUs running SEV guest Zheyun Shen
2025-02-06 22:05 ` Tom Lendacky
2025-02-26 1:20 ` Sean Christopherson
2025-02-26 3:26 ` Zheyun Shen
2025-02-26 23:58 ` Sean Christopherson
2025-02-26 1:37 ` [PATCH v7 0/3] " Sean Christopherson
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=Z75niMjZTQQ28HKP@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=kevinloughlin@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=szy0127@sjtu.edu.cn \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
/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