[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALMp9eTmAR_yMMxujiMDQ6_VpUF3ghoKAdy_SYvu-QOAThntZA@mail.gmail.com>
Date: Wed, 8 Nov 2023 10:19:39 -0800
From: Jim Mattson <jmattson@...gle.com>
To: Alexander Graf <graf@...zon.com>
Cc: Sean Christopherson <seanjc@...gle.com>,
Nicolas Saenz Julienne <nsaenz@...zon.com>,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-hyperv@...r.kernel.org, pbonzini@...hat.com,
vkuznets@...hat.com, anelkz@...zon.com, dwmw@...zon.co.uk,
jgowans@...zon.com, corbert@....net, kys@...rosoft.com,
haiyangz@...rosoft.com, decui@...rosoft.com, x86@...nel.org,
linux-doc@...r.kernel.org
Subject: Re: [RFC 29/33] KVM: VMX: Save instruction length on EPT violation
On Wed, Nov 8, 2023 at 9:27 AM Alexander Graf <graf@...zon.com> wrote:
> My point with the comment on this patch was "Don't break AMD (or ancient
> VMX without instruction length decoding [Does that exist? I know SVM has
> old CPUs that don't do it]) please".
VM-exit instruction length is not defined for all VM-exit reasons (EPT
misconfiguration is one that is notably absent), but the field has
been there since Prescott.
Powered by blists - more mailing lists