From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Zachary Amsden <zach@vmware.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.osdl.org>,
Andrew Morton <akpm@osdl.org>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [patch 3/9] Guest page hinting: volatile page cache.
Date: Mon, 18 Sep 2006 10:08:17 +0200 [thread overview]
Message-ID: <1158566897.5728.2.camel@localhost> (raw)
In-Reply-To: <200609151352_MC3-1-CB54-526A@compuserve.com>
On Fri, 2006-09-15 at 13:50 -0400, Chuck Ebbert wrote:
> > I wonder which trick you use, since there is only one page table one
> > i386 I can only imagine that you are tracking all page tables of the
> > guest.
>
> AMD K8 with the SVM feature has host and guest page tables and
> address-space identifiers for the guests so their global TLB flushes
> can be limited to their own address space...
Yeah, I know about the nested page tables on K8. But VMware will not
restrict themselves to K8 only, so they need a clever way to implement
shadow page tables on i386 chips without this feature.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries Development & Services
IBM Deutschland Entwicklung GmbH
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2006-09-18 8:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 17:50 [patch 3/9] Guest page hinting: volatile page cache Chuck Ebbert
2006-09-18 8:08 ` Martin Schwidefsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-01 11:09 Martin Schwidefsky
2006-09-01 14:54 ` Dave Hansen
2006-09-01 14:54 ` Dave Hansen
2006-09-01 15:29 ` Martin Schwidefsky
2006-09-01 15:37 ` Dave Hansen
2006-09-01 14:57 ` Dave Hansen
2006-09-01 15:31 ` Martin Schwidefsky
2006-09-01 15:48 ` Andy Whitcroft
2006-09-01 15:48 ` Andy Whitcroft
2006-09-01 16:04 ` Martin Schwidefsky
2006-09-01 16:04 ` Martin Schwidefsky
2006-09-01 16:18 ` Dave Hansen
2006-09-01 16:18 ` Dave Hansen
2006-09-01 16:25 ` Martin Schwidefsky
2006-09-01 16:37 ` Dave Hansen
2006-09-01 16:37 ` Dave Hansen
2006-09-01 16:56 ` Martin Schwidefsky
2006-09-01 17:16 ` Dave Hansen
2006-09-01 17:16 ` Dave Hansen
2006-09-01 17:42 ` Martin Schwidefsky
2006-09-01 18:03 ` Dave Hansen
2006-09-01 18:04 ` Martin Schwidefsky
2006-09-01 18:23 ` Dave Hansen
2006-09-01 18:23 ` Dave Hansen
2006-09-01 18:31 ` Martin Schwidefsky
2006-09-01 18:41 ` Dave Hansen
2006-09-04 11:21 ` Martin Schwidefsky
2006-09-05 18:27 ` Dave Hansen
2006-09-06 10:49 ` Martin Schwidefsky
2006-09-01 16:29 ` Dave Hansen
2006-09-01 17:02 ` Martin Schwidefsky
2006-09-01 17:05 ` Dave Hansen
2006-09-13 18:21 ` Zachary Amsden
2006-09-14 8:56 ` Martin Schwidefsky
2006-09-14 9:23 ` Zachary Amsden
2006-09-15 8:36 ` Martin Schwidefsky
2006-08-24 14:30 Martin Schwidefsky, Martin Schwidefsky, Hubertus Franke, Himanshu Raj
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=1158566897.5728.2.camel@localhost \
--to=schwidefsky@de.ibm.com \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=virtualization@lists.osdl.org \
--cc=zach@vmware.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.