From: Sean Christopherson <seanjc@google.com>
To: Krish Sadhukhan <krish.sadhukhan@oracle.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, jmattson@google.com
Subject: Re: [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 23:12:14 +0000 [thread overview]
Message-ID: <YGZTTvlMuB5Oo63C@google.com> (raw)
In-Reply-To: <20210401192033.91150-1-krish.sadhukhan@oracle.com>
On Thu, Apr 01, 2021, Krish Sadhukhan wrote:
> 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()
The kernel patches need to be rebased, their base is very stale and none of them
apply on kvm/queue.
prev parent reply other threads:[~2021-04-01 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 19:20 [PATCH 0/5 v5] KVM: nSVM: Check addresses of MSR bitmap and IO bitmap tables on vmrun of nested guests Krish Sadhukhan
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 ` Sean Christopherson [this message]
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=YGZTTvlMuB5Oo63C@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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 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).