[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZuSOaTw1vgwquqTE@google.com>
Date: Fri, 13 Sep 2024 12:11:37 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Nicolas Saenz Julienne <nsaenz@...zon.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org, pbonzini@...hat.com,
vkuznets@...hat.com, linux-doc@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-arch@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
graf@...zon.de, dwmw2@...radead.org, paul@...zon.com, mlevitsk@...hat.com,
jgowans@...zon.com, corbet@....net, decui@...rosoft.com, tglx@...utronix.de,
mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com, x86@...nel.org,
amoorthy@...gle.com
Subject: Re: [PATCH 11/18] KVM: x86: Pass the instruction length on memory
fault user-space exits
On Sun, Jun 09, 2024, Nicolas Saenz Julienne wrote:
> In order to simplify Hyper-V VSM secure memory intercept generation in
> user-space (it avoids the need of implementing an x86 instruction
> decoder and the actual decoding). Pass the instruction length being run
> at the time of the guest exit as part of the memory fault exit
> information.
Why does userspace need the instruction length, but not the associated code stream?
Powered by blists - more mailing lists