[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <167409102513.2376237.18253375780531585777.b4-ty@google.com>
Date: Thu, 19 Jan 2023 21:01:25 +0000
From: Sean Christopherson <seanjc@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>, x86@...nel.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org,
Vishal Annapurve <vannapurve@...gle.com>
Cc: pbonzini@...hat.com, shuah@...nel.org, bgardon@...gle.com,
peterx@...hat.com, vkuznets@...hat.com, dmatlack@...gle.com,
pgonda@...gle.com, andrew.jones@...ux.dev,
Oliver Upton <oliver.upton@...ux.dev>
Subject: Re: [V5 PATCH 0/3] Execute hypercalls according to host cpu
On Wed, 11 Jan 2023 00:44:42 +0000, Vishal Annapurve wrote:
> Confidential VMs(CVMs) need to execute hypercall instruction as per the CPU
> type. Normally KVM emulates the vmcall/vmmcall instruction by patching
> the guest code at runtime. Such a guest memory manipulation by KVM is
> not allowed with CVMs and is also undesirable in general.
>
> This series adds support of executing hypercall as per the host cpu vendor.
> CPU vendor is queried early during selftest setup and guest setup to be
> reused later.
>
> [...]
Applied to kvm-x86 selftests, thanks!
[1/3] KVM: selftests: x86: Use "this_cpu" prefix for cpu vendor queries
https://github.com/kvm-x86/linux/commit/093db78b8e6b
[2/3] KVM: selftests: x86: Cache host CPU vendor (AMD vs. Intel)
https://github.com/kvm-x86/linux/commit/832ffb370183
[3/3] KVM: selftests: x86: Use host's native hypercall instruction in kvm_hypercall()
https://github.com/kvm-x86/linux/commit/019dfeb31650
--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes
Powered by blists - more mailing lists