kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jim Mattson <jmattson@google.com>
To: Aaron Lewis <aaronlewis@google.com>
Cc: David Edmondson <david.edmondson@oracle.com>,
	Sean Christopherson <seanjc@google.com>,
	kvm list <kvm@vger.kernel.org>
Subject: Re: [PATCH v6 1/2] kvm: x86: Allow userspace to handle emulation errors
Date: Thu, 3 Jun 2021 13:35:01 -0700	[thread overview]
Message-ID: <CALMp9eQ_42r-S-JPD-n7oXEaeMRVZdUG1UQkYJkhmHCSUkjvrw@mail.gmail.com> (raw)
In-Reply-To: <20210510144834.658457-2-aaronlewis@google.com>

On Mon, May 10, 2021 at 7:48 AM Aaron Lewis <aaronlewis@google.com> wrote:
>
> Add a fallback mechanism to the in-kernel instruction emulator that
> allows userspace the opportunity to process an instruction the emulator
> was unable to.  When the in-kernel instruction emulator fails to process
> an instruction it will either inject a #UD into the guest or exit to
> userspace with exit reason KVM_INTERNAL_ERROR.  This is because it does
> not know how to proceed in an appropriate manner.  This feature lets
> userspace get involved to see if it can figure out a better path
> forward.
>
> Signed-off-by: Aaron Lewis <aaronlewis@google.com>
> Reviewed-by: David Edmondson <david.edmondson@oracle.com>
Reviewed-by: Jim Mattson <jmattson@google.com>

  reply	other threads:[~2021-06-03 20:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 14:48 [PATCH v6 0/2] fallback for emulation errors Aaron Lewis
2021-05-10 14:48 ` [PATCH v6 1/2] kvm: x86: Allow userspace to handle " Aaron Lewis
2021-06-03 20:35   ` Jim Mattson [this message]
2021-06-23 17:44     ` Aaron Lewis
2021-06-23 21:38       ` Paolo Bonzini
2021-05-10 14:48 ` [PATCH v6 2/2] selftests: kvm: Allows " Aaron Lewis
2021-06-23 21:44 ` [PATCH v6 0/2] fallback for " Paolo Bonzini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALMp9eQ_42r-S-JPD-n7oXEaeMRVZdUG1UQkYJkhmHCSUkjvrw@mail.gmail.com \
    --to=jmattson@google.com \
    --cc=aaronlewis@google.com \
    --cc=david.edmondson@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=seanjc@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).