[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <73338ff4-24b0-0358-0419-ad0fb0101813@redhat.com>
Date: Mon, 7 Aug 2023 09:03:12 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Chao Gao <chao.gao@...el.com>,
Yang Weijiang <weijiang.yang@...el.com>, peterz@...radead.org,
john.allen@....com, kvm@...r.kernel.org,
linux-kernel@...r.kernel.org, rick.p.edgecombe@...el.com,
binbin.wu@...ux.intel.com
Subject: Re: [PATCH v5 11/19] KVM:VMX: Emulate read and write to CET MSRs
On 8/5/23 00:21, Sean Christopherson wrote:
> Oooh, the MSRs that don't exempt host_initiated are added to the list
(are *not* added)
> of MSRs to save/restore, i.e. KVM "silently" supports
> MSR_AMD64_OSVW_ID_LENGTH and MSR_AMD64_OSVW_STATUS.
>
> And guest_pv_has() returns true unless userspace has opted in to
> enforcement.
Two different ways of having the same bug. The latter was introduced in
the implementation of KVM_CAP_ENFORCE_PV_FEATURE_CPUID; it would become
a problem if some selftests started using it.
Paolo
Powered by blists - more mailing lists