From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: MMU: Document large pages
Date: Tue, 1 Jun 2010 16:33:42 -0300 [thread overview]
Message-ID: <20100601193342.GA30290@amt.cnet> (raw)
In-Reply-To: <1274967852-31886-1-git-send-email-avi@redhat.com>
On Thu, May 27, 2010 at 04:44:12PM +0300, Avi Kivity wrote:
> Signed-off-by: Avi Kivity <avi@redhat.com>
> ---
> Documentation/kvm/mmu.txt | 23 +++++++++++++++++++++++
> 1 files changed, 23 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/kvm/mmu.txt b/Documentation/kvm/mmu.txt
> index 1e7ecdd..6a0cab2 100644
> --- a/Documentation/kvm/mmu.txt
> +++ b/Documentation/kvm/mmu.txt
> @@ -317,6 +317,29 @@ on fault type:
>
> (user write faults generate a #PF)
>
> +Large pages
> +===========
> +
> +The mmu supports all combinations of large and small guest and host pages.
> +Supported page sizes include 4k, 2M, 4M, and 1G. 4M pages are treated as
> +two separate 2M pages, on both guest and host, since the mmu always uses PAE
> +paging.
> +
> +To instantiate a large spte, four constraints must be satisfied:
> +
> +- the spte must point to a large host page
> +- the guest pte must be a large pte of at least equivalent size (if tdp is
> + enabled, there is no guest pte and this condition is satisified)
> +- if the spte will be writeable, the large page frame may not overlap any
> + write-protected pages
> +- the guest guest pte must be wholly contained by a single memory slot
Fixed this "guest guest pte" typo and applied.
prev parent reply other threads:[~2010-06-01 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 13:44 [PATCH] KVM: MMU: Document large pages Avi Kivity
2010-06-01 19:33 ` Marcelo Tosatti [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=20100601193342.GA30290@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=xiaoguangrong@cn.fujitsu.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).