[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALMp9eRTy-m6DkXRSGNU=r7xmrzFFQU60DB2asUDZLCgw93wRQ@mail.gmail.com>
Date: Mon, 12 Apr 2021 11:34:33 -0700
From: Jim Mattson <jmattson@...gle.com>
To: David Edmondson <david.edmondson@...cle.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
kvm list <kvm@...r.kernel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"the arch/x86 maintainers" <x86@...nel.org>,
Sean Christopherson <seanjc@...gle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Joerg Roedel <joro@...tes.org>,
Wanpeng Li <wanpengli@...cent.com>,
Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>,
Aaron Lewis <aaronlewis@...gle.com>
Subject: Re: [PATCH 0/6] KVM: x86: Make the cause of instruction emulation
available to user-space
On Mon, Apr 12, 2021 at 6:09 AM David Edmondson
<david.edmondson@...cle.com> wrote:
>
> Instruction emulation happens for a variety of reasons, yet on error
> we have no idea exactly what triggered it. Add a cause of emulation to
> the various originators and pass it upstream when emulation fails.
What is userspace going to do with this information? It's hard to say
whether or not this is the right ABI without more context.
Powered by blists - more mailing lists