From: "Stefan Sterz" <s.sterz@proxmox.com>
To: "Sean Christopherson" <seanjc@google.com>,
"Paolo Bonzini" <pbonzini@redhat.com>
Cc: <kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] KVM: nSVM: TLB_CONTROL / FLUSHBYASID "fixes"
Date: Thu, 19 Oct 2023 15:12:23 +0200 [thread overview]
Message-ID: <CWCFRS30GBXB.2KV4ZAWTFNZTO@erna> (raw)
In-Reply-To: <20231018194104.1896415-1-seanjc@google.com>
On Wed Oct 18, 2023 at 9:41 PM CEST, Sean Christopherson wrote:
> Two "fixes" to play nice with running VMware Workstation on top of KVM,
> in quotes because patch 2 isn't really a fix.
>
Hey, thanks for providing these patches. Tested them here with ESXi 7,
they work like a charm!
As a sidenote regarding my tests: had to fiddle a bit with the reverted
commit as I applied them on top of the v6.2 tag, because that is still
the kernel version we use over here.
> Sean Christopherson (2):
> Revert "nSVM: Check for reserved encodings of TLB_CONTROL in nested
> VMCB"
> KVM: nSVM: Advertise support for flush-by-ASID
>
> arch/x86/kvm/svm/nested.c | 15 ---------------
> arch/x86/kvm/svm/svm.c | 1 +
> 2 files changed, 1 insertion(+), 15 deletions(-)
>
>
> base-commit: 437bba5ad2bba00c2056c896753a32edf80860cc
> --
> 2.42.0.655.g421f12c284-goog
next prev parent reply other threads:[~2023-10-19 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 19:41 [PATCH 0/2] KVM: nSVM: TLB_CONTROL / FLUSHBYASID "fixes" Sean Christopherson
2023-10-18 19:41 ` [PATCH 1/2] Revert "nSVM: Check for reserved encodings of TLB_CONTROL in nested VMCB" Sean Christopherson
2023-11-20 11:41 ` Maxim Levitsky
2023-10-18 19:41 ` [PATCH 2/2] KVM: nSVM: Advertise support for flush-by-ASID Sean Christopherson
2023-11-20 11:42 ` Maxim Levitsky
2023-10-19 13:12 ` Stefan Sterz [this message]
2023-12-01 1:52 ` [PATCH 0/2] KVM: nSVM: TLB_CONTROL / FLUSHBYASID "fixes" 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=CWCFRS30GBXB.2KV4ZAWTFNZTO@erna \
--to=s.sterz@proxmox.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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