From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [patch 0/4] add e500 platform support for KVM
Date: Tue, 09 Sep 2008 11:08:05 +0000 [thread overview]
Message-ID: <200809090608.05545.hollisb@us.ibm.com> (raw)
In-Reply-To: <1218790228-19549-1-git-send-email-yu.liu@freescale.com>
On Monday 08 September 2008 21:08:02 Liu Yu-B13201 wrote:
>
> > You can't assume that TLB1 does not contain user mappings, because
> > that's not true with hugetlbfs. Of course, hugetlbfs doesn't (yet?)
> > exist for e500, so the assumption is valid until that happens.
> >
> > However, we *really* need large host page mappings to make KVM fast.
> > Right now we have to split guest large pages (covering the
> > kernel) into
> > lots of 4K mappings, which means our TLB miss rate is *much*
> > higher than
> > if we could use hugetlbfs on the host. In that case, we could use
> > hugetlbfs large user pages to back the guest kernel mappings.
> >
>
> Yes. It's a problem. But I afraid e500 would not use hugetlbfs,
> as it means to give up 512-entry TLB0, while TLB1 has only 16 entries.
I don't think you'd need to "give up" anything -- some parts of user memory
would be backed with 4K pages, and some parts with large pages.
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2008-09-09 11:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 8:50 [patch 0/4] add e500 platform support for KVM Liu Yu
2008-08-21 20:54 ` Hollis Blanchard
2008-08-22 11:00 ` Liu Yu
2008-08-29 17:09 ` Hollis Blanchard
2008-08-30 3:15 ` Liu Yu
2008-09-08 17:30 ` Hollis Blanchard
2008-09-09 2:08 ` Liu Yu-B13201
2008-09-09 11:08 ` Hollis Blanchard [this message]
2008-09-11 8:43 ` Liu Yu-B13201
2008-09-11 14:45 ` Hollis Blanchard
2008-09-12 2:28 ` Liu Yu-B13201
2008-09-12 2:31 ` Liu Yu-B13201
2008-09-12 14:49 ` Hollis Blanchard
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=200809090608.05545.hollisb@us.ibm.com \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
/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