All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Manali Shukla <manali.shukla@amd.com>
Cc: pbonzini@redhat.com, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH v5 0/8] Move npt test cases and NPT code improvements
Date: Thu, 21 Jul 2022 19:15:31 +0000	[thread overview]
Message-ID: <Ytml0zc1cJh5tRG9@google.com> (raw)
In-Reply-To: <20220628113853.392569-1-manali.shukla@amd.com>

On Tue, Jun 28, 2022, Manali Shukla wrote:
> If __setup_vm() is changed to setup_vm(), KUT will build tests with PT_USER_MASK
> set on all PTEs. It is a better idea to move nNPT tests to their own file so
> that tests don't need to fiddle with page tables midway.
> 
> The quick approach to do this would be to turn the current main into a small
> helper, without calling __setup_vm() from helper.
> 
> setup_mmu_range() function in vm.c was modified to allocate new user pages to
> implement nested page table.
> 
> Current implementation of nested page table does the page table build up
> statically with 2048 PTEs and one pml4 entry. With newly implemented routine,
> nested page table can be implemented dynamically based on the RAM size of VM
> which enables us to have separate memory ranges to test various npt test cases.
> 
> Based on this implementation, minimal changes were required to be done in
> below mentioned existing APIs:
> npt_get_pde(), npt_get_pte(), npt_get_pdpe().

I have a variety of nits and minor complaints, but no need to send another version,
I'll fix things up as I go.  I'm going to send Paolo a pull request for KUT, there's
a big pile of outstanding changes that have been languishing.

  parent reply	other threads:[~2022-07-21 19:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 11:38 [kvm-unit-tests PATCH v5 0/8] Move npt test cases and NPT code improvements Manali Shukla
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 1/8] x86: nSVM: Move common functionality of the main() to helper run_svm_tests Manali Shukla
2022-07-21 18:04   ` Sean Christopherson
2022-07-21 19:13   ` Sean Christopherson
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 2/8] x86: nSVM: Move all nNPT test cases from svm_tests.c to a separate file Manali Shukla
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 3/8] x86: nSVM: Allow nSVM tests run with PT_USER_MASK enabled Manali Shukla
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 4/8] x86: Improve set_mmu_range() to implement npt Manali Shukla
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 5/8] x86: nSVM: Build up the nested page table dynamically Manali Shukla
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 6/8] x86: nSVM: Correct indentation for svm.c Manali Shukla
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 7/8] x86: nSVM: Correct indentation for svm_tests.c part-1 Manali Shukla
2022-06-28 11:38 ` [kvm-unit-tests PATCH v5 8/8] x86: nSVM: Correct indentation for svm_tests.c part-2 Manali Shukla
2022-07-12 16:35 ` [kvm-unit-tests PATCH v5 0/8] Move npt test cases and NPT code improvements Shukla, Manali
2022-07-21 19:15 ` Sean Christopherson [this message]
2022-07-22 13:00   ` Shukla, Manali

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=Ytml0zc1cJh5tRG9@google.com \
    --to=seanjc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=manali.shukla@amd.com \
    --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 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.