From: Mingwei Zhang <mizhang@google.com>
To: "Huang, Kai" <kai.huang@intel.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>, "Christopherson,,
Sean" <seanjc@google.com>,
"jmattson@google.com" <jmattson@google.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dmatlack@google.com" <dmatlack@google.com>,
"bgardon@google.com" <bgardon@google.com>
Subject: Re: [PATCH 6/6] KVM: Documentation: Add the missing tdp_mmu_page into kvm_mmu_page
Date: Mon, 26 Jun 2023 17:59:54 +0000 [thread overview]
Message-ID: <ZJnSGrskpTjhZ3qV@google.com> (raw)
In-Reply-To: <4e2eae9ab23748ea32fe07d39a704d65d50a0973.camel@intel.com>
On Thu, Jun 22, 2023, Huang, Kai wrote:
> On Sun, 2023-06-18 at 00:08 +0000, Mingwei Zhang wrote:
> > Add tdp_mmu_page into kvm_mmu_page description. tdp_mmu_page is a field to
> > differentiate shadow pages from TDP MMU and non-TDP MMU. When TDP MMU is
> > enabled, sp->tdp_mmu_page=1 indicates a shadow page for L1, while
> > sp->tdp_mmu_page=0 indicates a shadow page for an L2. When TDP MMU is
> > disabled, sp->tdp_mmu_page is always 0. So update the doc to reflect the
> > information.
> >
> > Signed-off-by: Mingwei Zhang <mizhang@google.com>
> > ---
> > Documentation/virt/kvm/x86/mmu.rst | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/Documentation/virt/kvm/x86/mmu.rst b/Documentation/virt/kvm/x86/mmu.rst
> > index 0dbdb7fb8cc6..cbad49c37629 100644
> > --- a/Documentation/virt/kvm/x86/mmu.rst
> > +++ b/Documentation/virt/kvm/x86/mmu.rst
> > @@ -277,6 +277,10 @@ Shadow pages contain the following information:
> > since the last time the page table was actually used; if emulation
> > is triggered too frequently on this page, KVM will unmap the page
> > to avoid emulation in the future.
> > + tdp_mmu_page:
> > + Is 1 if the shadow page is a TDP MMU page. When TDP MMU is disabled,
> > + this field is always 0.
> > +
> >
>
> Hmm.. Again I think "TDP MMU is disabled" is a little bit confusing, but maybe
> it's only me having this impression.
>
> I think you can just delete the second sentence.
It is not confusing but redundant in this case. I will delete it in next
version.
next prev parent reply other threads:[~2023-06-26 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 0:08 [PATCH 0/6] KVM: Documentation: Update document description for kvm_mmu_page and kvm_mmu_page_role Mingwei Zhang
2023-06-18 0:08 ` [PATCH 1/6] KVM: Documentation: Add the missing guest_mode in kvm_mmu_page_role Mingwei Zhang
2023-06-22 8:22 ` Huang, Kai
2023-06-18 0:08 ` [PATCH 2/6] KVM: Documentation: Update the field name gfns in kvm_mmu_page Mingwei Zhang
2023-06-22 8:22 ` Huang, Kai
2023-06-23 0:30 ` Xu Yilun
2023-06-23 0:55 ` Xu Yilun
2023-06-26 17:06 ` Mingwei Zhang
2023-06-18 0:08 ` [PATCH 3/6] KVM: Documentation: Add the missing ptep " Mingwei Zhang
2023-06-22 8:32 ` Huang, Kai
2023-06-26 17:29 ` Mingwei Zhang
2023-06-18 0:08 ` [PATCH 4/6] KVM: Documentation: Add the missing tdp_mmu_root_count into kvm_mmu_page Mingwei Zhang
2023-06-22 8:37 ` Huang, Kai
2023-06-26 17:55 ` Mingwei Zhang
2023-06-18 0:08 ` [PATCH 5/6] KVM: Documentation: Add the missing mmu_valid_gen " Mingwei Zhang
2023-06-22 8:42 ` Huang, Kai
2023-06-18 0:08 ` [PATCH 6/6] KVM: Documentation: Add the missing tdp_mmu_page " Mingwei Zhang
2023-06-22 8:40 ` Huang, Kai
2023-06-26 17:59 ` Mingwei Zhang [this message]
2023-06-19 9:00 ` [PATCH 0/6] KVM: Documentation: Update document description for kvm_mmu_page and kvm_mmu_page_role Zhi Wang
2023-06-21 18:33 ` 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=ZJnSGrskpTjhZ3qV@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 \
/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).