mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: jmattson@google.com
Subject: [PATCH v7 0/4] Raise #UD and disable execution controls for more CPUID bits
Date: Thu, 24 Aug 2017 15:37:55 +0200	[thread overview]
Message-ID: <1503581879-52125-1-git-send-email-pbonzini@redhat.com> (raw)

Usually we're not that particular about #UD-ing on disabled instructions,
because you cannot do it for all instructions.  However, whenever an
instruction has a corresponding execution control it is important to do
it for the sake of getting vmexits right.

Paolo

Jim Mattson (2):
  kvm: vmx: Raise #UD on unsupported RDRAND
  kvm: vmx: Raise #UD on unsupported RDSEED

Paolo Bonzini (2):
  KVM: VMX: cache secondary exec controls
  kvm: vmx: Raise #UD on unsupported XSAVES/XRSTORS

 arch/x86/kvm/vmx.c | 175 +++++++++++++++++++++++++++++++++++++----------------
 1 file changed, 124 insertions(+), 51 deletions(-)

-- 
1.8.3.1

             reply	other threads:[~2017-08-24 13:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24 13:37 Paolo Bonzini [this message]
2017-08-24 13:37 ` [PATCH 1/4] KVM: VMX: cache secondary exec controls Paolo Bonzini
2017-08-24 14:47   ` Jim Mattson
2017-08-24 15:25     ` Paolo Bonzini
2017-08-24 15:41       ` Jim Mattson
2017-08-24 15:46         ` Paolo Bonzini
2017-08-24 16:02           ` Jim Mattson
2017-08-24 16:08             ` Paolo Bonzini
2017-08-24 13:37 ` [PATCH 2/4] kvm: vmx: Raise #UD on unsupported RDRAND Paolo Bonzini
2017-08-24 17:42   ` David Hildenbrand
2017-08-24 13:37 ` [PATCH 3/4] kvm: vmx: Raise #UD on unsupported RDSEED Paolo Bonzini
2017-08-24 17:42   ` David Hildenbrand
2017-08-24 13:37 ` [PATCH 4/4] kvm: vmx: Raise #UD on unsupported XSAVES/XRSTORS Paolo Bonzini
2017-08-24 14:54   ` Jim Mattson
2017-08-24 16:09     ` [PATCH v8 " Paolo Bonzini
2017-08-24 20:41       ` Jim Mattson

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=1503581879-52125-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®