[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cunk0p6sbdq.fsf@dme.org>
Date: Tue, 13 Apr 2021 11:54:25 +0100
From: David Edmondson <dme@....org>
To: Jim Mattson <jmattson@...gle.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 Monday, 2021-04-12 at 11:34:33 -07, Jim Mattson wrote:
> 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.
Logging for debug purposes, see reply to Sean.
dme.
--
You make me feel like a natural woman.
Powered by blists - more mailing lists