All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krish Sadhukhan <krish.sadhukhan@oracle.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, jmattson@google.com, seanjc@google.com
Subject: [PATCH 0/5 v5] KVM: nSVM: Check addresses of MSR bitmap and IO bitmap tables on vmrun of nested guests
Date: Thu,  1 Apr 2021 15:20:28 -0400	[thread overview]
Message-ID: <20210401192033.91150-1-krish.sadhukhan@oracle.com> (raw)

v4 -> v5:
        1. In patch# 1, the actual size of the MSRPM and IOPM tables are now
	   defined. The initialization code for the tables has been adjusted
	   accordingly.
	2. In patch# 2, the checks have been adjusted based on the actual
	   size of the tables. The check for IOPM has also been fixed.
	3. In patch# 4, a new test case has been added. This new test uses
	   an address whose last byte touched the limit of the maximum
	   physical address.

[PATCH 1/5 v5] KVM: SVM: Define actual size of IOPM and MSRPM tables
[PATCH 2/5 v5] nSVM: Check addresses of MSR and IO permission maps
[PATCH 3/5 v5] KVM: nSVM: Cleanup in nested_svm_vmrun()
[PATCH 4/5 v5] nSVM: Test addresses of MSR and IO permissions maps
[PATCH 5/5 v5] SVM: Use ALIGN macro when aligning 'io_bitmap_area'

 arch/x86/kvm/svm/nested.c | 59 +++++++++++++++++++++++++++++------------------
 arch/x86/kvm/svm/svm.c    | 20 ++++++++--------
 arch/x86/kvm/svm/svm.h    |  3 +++
 3 files changed, 50 insertions(+), 32 deletions(-)

Krish Sadhukhan (3):
      KVM: SVM: Define actual size of IOPM and MSRPM tables
      nSVM: Check addresses of MSR and IO permission maps
      KVM: nSVM: Cleanup in nested_svm_vmrun()

 x86/svm.c       |  2 +-
 x86/svm_tests.c | 42 +++++++++++++++++++++++++++++++++++++++++-
 2 files changed, 42 insertions(+), 2 deletions(-)

Krish Sadhukhan (2):
      nSVM: Test addresses of MSR and IO permissions maps
      SVM: Use ALIGN macro when aligning 'io_bitmap_area'


             reply	other threads:[~2021-04-01 20:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 19:20 Krish Sadhukhan [this message]
2021-04-01 19:20 ` [PATCH 1/5 v5] KVM: SVM: Define actual size of IOPM and MSRPM tables Krish Sadhukhan
2021-04-01 19:20 ` [PATCH 2/5 v5] nSVM: Check addresses of MSR and IO permission maps Krish Sadhukhan
2021-04-01 19:20 ` [PATCH 3/5 v5] KVM: nSVM: Cleanup in nested_svm_vmrun() Krish Sadhukhan
2021-04-01 19:20 ` [PATCH 4/5 v5] nSVM: Test addresses of MSR and IO permissions maps Krish Sadhukhan
2021-04-01 19:20 ` [PATCH 5/5 v5] SVM: Use ALIGN macro when aligning 'io_bitmap_area' Krish Sadhukhan
2021-04-01 23:12 ` [PATCH 0/5 v5] KVM: nSVM: Check addresses of MSR bitmap and IO bitmap tables on vmrun of nested guests Sean Christopherson

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=20210401192033.91150-1-krish.sadhukhan@oracle.com \
    --to=krish.sadhukhan@oracle.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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 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.