kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Babu Moger <babu.moger@amd.com>
To: Cathy Avery <cavery@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>
Cc: "vkuznets@redhat.com" <vkuznets@redhat.com>,
	"Huang2, Wei" <Wei.Huang2@amd.com>,
	"mlevitsk@redhat.com" <mlevitsk@redhat.com>,
	"sean.j.christopherson@intel.com"
	<sean.j.christopherson@intel.com>
Subject: RE: [PATCH v3 0/2] KVM: SVM: Create separate vmcbs for L1 and L2
Date: Wed, 11 Nov 2020 15:35:49 -0600	[thread overview]
Message-ID: <75b85cc7-96d9-eab9-9748-715ed951034d@amd.com> (raw)
In-Reply-To: <20201026174222.21811-1-cavery@redhat.com>

Hi Cathy,
I was going to test these patches. But it did not apply on my tree.
Tried on kvm(https://git.kernel.org/pub/scm/virt/kvm/kvm.git) and
Mainline
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git). What
is your base tree?
thanks
Babu

> -----Original Message-----
> From: Cathy Avery <cavery@redhat.com>
> Sent: Monday, October 26, 2020 12:42 PM
> To: linux-kernel@vger.kernel.org; kvm@vger.kernel.org; pbonzini@redhat.com
> Cc: vkuznets@redhat.com; Huang2, Wei <Wei.Huang2@amd.com>;
> mlevitsk@redhat.com; sean.j.christopherson@intel.com
> Subject: [PATCH v3 0/2] KVM: SVM: Create separate vmcbs for L1 and L2
> 
> svm->vmcb will now point to either a separate vmcb L1 ( not nested ) or L2 vmcb
> ( nested ).
> 
> Changes:
> v2 -> v3
>  - Added vmcb switching helper.
>  - svm_set_nested_state always forces to L1 before determining state
>    to set. This is more like vmx and covers any potential L2 to L2 nested state
> switch.
>  - Moved svm->asid tracking to pre_svm_run and added ASID set dirty bit
>    checking.
> 
> v1 -> v2
>  - Removed unnecessary update check of L1 save.cr3 during nested_svm_vmexit.
>  - Moved vmcb01_pa to svm.
>  - Removed get_host_vmcb() function.
>  - Updated vmsave/vmload corresponding vmcb state during L2
>    enter and exit which fixed the L2 load issue.
>  - Moved asid workaround to a new patch which adds asid to svm.
>  - Init previously uninitialized L2 vmcb save.gpat and save.cr4
> 
> Tested:
> kvm-unit-tests
> kvm self tests
> Loaded fedora nested guest on fedora
> 
> Cathy Avery (2):
>   KVM: SVM: Track asid from vcpu_svm
>   KVM: SVM: Use a separate vmcb for the nested L2 guest
> 
>  arch/x86/kvm/svm/nested.c | 125 ++++++++++++++++++--------------------
>  arch/x86/kvm/svm/svm.c    |  58 +++++++++++-------
>  arch/x86/kvm/svm/svm.h    |  51 +++++-----------
>  3 files changed, 110 insertions(+), 124 deletions(-)
> 
> --
> 2.20.1


  parent reply	other threads:[~2020-11-11 21:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-26 17:42 [PATCH v3 0/2] KVM: SVM: Create separate vmcbs for L1 and L2 Cathy Avery
2020-10-26 17:42 ` [PATCH v3 1/2] KVM: SVM: Track asid from vcpu_svm Cathy Avery
2020-10-26 17:42 ` [PATCH v3 2/2] KVM: SVM: Use a separate vmcb for the nested L2 guest Cathy Avery
2020-11-11 21:35 ` Babu Moger [this message]
2020-11-12 13:52   ` [PATCH v3 0/2] KVM: SVM: Create separate vmcbs for L1 and L2 Cathy Avery

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=75b85cc7-96d9-eab9-9748-715ed951034d@amd.com \
    --to=babu.moger@amd.com \
    --cc=Wei.Huang2@amd.com \
    --cc=cavery@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --cc=vkuznets@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).