From: Mingwei Zhang <mizhang@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Mingwei Zhang <mizhang@google.com>,
Kai Huang <kai.huang@intel.com>,
Jim Mattson <jmattson@google.com>,
David Matlack <dmatlack@google.com>,
Ben Gardon <bgardon@google.com>, Xu Yilun <yilun.xu@intel.com>,
Zhi Wang <zhi.wang.linux@gmail.com>
Subject: [PATCH v2 1/6] KVM: Documentation: Add the missing description for guest_mode in kvm_mmu_page_role
Date: Mon, 26 Jun 2023 18:20:11 +0000 [thread overview]
Message-ID: <20230626182016.4127366-2-mizhang@google.com> (raw)
In-Reply-To: <20230626182016.4127366-1-mizhang@google.com>
Add the missing description for guest_mode in kvm_mmu_page_role
description. guest_mode tells KVM whether a shadow page is used for the L1
or an L2. Update the missing field in documentation.
Signed-off-by: Mingwei Zhang <mizhang@google.com>
Reviewed-by: Kai Huang <kai.huang@intel.com>
---
Documentation/virt/kvm/x86/mmu.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/virt/kvm/x86/mmu.rst b/Documentation/virt/kvm/x86/mmu.rst
index 8364afa228ec..561efa8ec7d7 100644
--- a/Documentation/virt/kvm/x86/mmu.rst
+++ b/Documentation/virt/kvm/x86/mmu.rst
@@ -202,6 +202,8 @@ Shadow pages contain the following information:
Is 1 if the MMU instance cannot use A/D bits. EPT did not have A/D
bits before Haswell; shadow EPT page tables also cannot use A/D bits
if the L1 hypervisor does not enable them.
+ role.guest_mode:
+ Indicates the shadow page is created for a nested guest.
role.passthrough:
The page is not backed by a guest page table, but its first entry
points to one. This is set if NPT uses 5-level page tables (host
--
2.41.0.162.gfafddb0af9-goog
next prev parent reply other threads:[~2023-06-26 18:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 18:20 [PATCH v2 0/6] Update document description for kvm_mmu_page and kvm_mmu_page_role Mingwei Zhang
2023-06-26 18:20 ` Mingwei Zhang [this message]
2023-06-26 18:20 ` [PATCH v2 2/6] KVM: Documentation: Update the field name gfns and its description in kvm_mmu_page Mingwei Zhang
2023-06-26 21:49 ` Randy Dunlap
2023-07-31 17:54 ` Mingwei Zhang
2023-07-31 18:24 ` Sean Christopherson
2023-07-31 18:59 ` Mingwei Zhang
2023-06-26 18:20 ` [PATCH v2 3/6] KVM: Documentation: Add the missing description for ptep " Mingwei Zhang
2023-06-26 21:44 ` Randy Dunlap
2023-06-26 22:20 ` Huang, Kai
2023-06-27 15:27 ` Sean Christopherson
2023-07-31 18:09 ` Mingwei Zhang
2023-06-26 18:20 ` [PATCH v2 4/6] KVM: Documentation: Add the missing description for tdp_mmu_root_count into kvm_mmu_page Mingwei Zhang
2023-06-26 22:21 ` Huang, Kai
2023-06-27 15:50 ` Sean Christopherson
2023-07-31 18:41 ` Mingwei Zhang
2023-06-26 18:20 ` [PATCH v2 5/6] KVM: Documentation: Add the missing description for mmu_valid_gen " Mingwei Zhang
2023-06-27 16:13 ` Sean Christopherson
2023-07-31 22:02 ` Mingwei Zhang
2023-06-26 18:20 ` [PATCH v2 6/6] KVM: Documentation: Add the missing description for tdp_mmu_page " Mingwei Zhang
2023-06-26 22:23 ` Huang, Kai
2023-06-27 16:16 ` Sean Christopherson
2023-07-31 22:28 ` Mingwei Zhang
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=20230626182016.4127366-2-mizhang@google.com \
--to=mizhang@google.com \
--cc=bgardon@google.com \
--cc=dmatlack@google.com \
--cc=jmattson@google.com \
--cc=kai.huang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=yilun.xu@intel.com \
--cc=zhi.wang.linux@gmail.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).