From: Jeremy Fitzhardinge <jeremy@xensource.com>
To: carsteno@de.ibm.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
linux-mm@kvack.org, Peter Chubb <peterc@gelato.unsw.edu.au>,
virtualization@lists.linux-foundation.org,
Avi Kivity <avi@qumranet.com>
Subject: Re: RFC: multiple address spaces for one process
Date: Sat, 30 Jun 2007 09:30:42 -0700 [thread overview]
Message-ID: <46868532.7030208@xensource.com> (raw)
In-Reply-To: <4685D9C9.20504@de.ibm.com>
Carsten Otte wrote:
> The big difference here is that LinuxOnLinux does represent guest
> virtual addressing in these mm structs where all other kernel based
> VMMs do represent guest physical in the user address space. That
> somewhat disqualifies LinuxOnLinux to share the commonality.
> Whether or not proposed patch makes sense for shaddow page tables is
> unknown to me, since we have nested paging on s390.
From an interface perspective, I think nested paging and shadow
pagetables should be identical; after all, shadow pagetables are just a
software implementation of nested pagetables. There seem to be 3
distinct types of VMM pagetable:
1. UML/LoL vmas-as-pagetable/tlb
2. shadow/nested paging
3. direct paging
The multiple address space patch definitely makes sense for 1, but 2&3
both implement the alternate address space by directly pointing the
CPU's paging hardware at a new pagetable, rather than going via the
Linux VM.
J
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2007-06-30 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 11:08 Peter Chubb
2007-06-29 14:32 ` Jeremy Fitzhardinge
2007-06-30 4:19 ` Carsten Otte
2007-06-30 9:59 ` Peter Chubb
2007-06-30 16:30 ` Jeremy Fitzhardinge [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=46868532.7030208@xensource.com \
--to=jeremy@xensource.com \
--cc=avi@qumranet.com \
--cc=carsteno@de.ibm.com \
--cc=jeremy@goop.org \
--cc=linux-mm@kvack.org \
--cc=peterc@gelato.unsw.edu.au \
--cc=virtualization@lists.linux-foundation.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