All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: peterx@redhat.com
Subject: [PATCH 0/4] KVM: nSVM: more svm_check_nested_events work
Date: Sat, 16 May 2020 09:53:07 -0400	[thread overview]
Message-ID: <20200516135311.704878-1-pbonzini@redhat.com> (raw)

This moves exception injection to svm_check_nested_events, which is very
pleasing: it cleans up the recently introduced #DB handling, removes
exit_required, and fixes #UD trapping in the guest (for example
from an RSM instruction, as tested in kvm-unit-tests).

As a bonus, the last patch adds INIT vmexit injection to
svm_check_nested_events as well.  Note that there is no test case for
that yet.

The patches have small conflicts with those I posted yesterday, so
they are on top of them.

Paolo

Paolo Bonzini (4):
  KVM: nSVM: fix condition for filtering async PF
  KVM: nSVM: inject exceptions via svm_check_nested_events
  KVM: nSVM: remove exit_required
  KVM: nSVM: correctly inject INIT vmexits

 arch/x86/kvm/svm/nested.c | 159 ++++++++++++++++++--------------------
 arch/x86/kvm/svm/svm.c    |  23 ------
 arch/x86/kvm/svm/svm.h    |   4 +-
 3 files changed, 75 insertions(+), 111 deletions(-)

-- 
2.18.2


             reply	other threads:[~2020-05-16 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 13:53 Paolo Bonzini [this message]
2020-05-16 13:53 ` [PATCH 1/4] KVM: nSVM: fix condition for filtering async PF Paolo Bonzini
2020-05-18 15:05   ` Sean Christopherson
2020-05-16 13:53 ` [PATCH 2/4] KVM: nSVM: inject exceptions via svm_check_nested_events Paolo Bonzini
2020-05-16 13:53 ` [PATCH 3/4] KVM: nSVM: remove exit_required Paolo Bonzini
2020-05-16 13:53 ` [PATCH 4/4] KVM: nSVM: correctly inject INIT vmexits 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=20200516135311.704878-1-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterx@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.