From: Christian Limpach <chris@pin.lu>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Kip Macy <kmacy@fsmware.com>,
"MAGENHEIMER,DAN (HP-FtCollins, ex1)" <dan.magenheimer@hp.com>,
xen-devel@lists.sourceforge.net
Subject: Re: Xen at scale
Date: Wed, 24 Mar 2004 13:12:09 +0100 [thread overview]
Message-ID: <0b4e01c41199$3c84a150$070414ac@pin> (raw)
In-Reply-To: E1B65x2-0000IJ-00@mta1.cl.cam.ac.uk
> It needs to be something other than page tables, really. I'm inclined
> to pass the new domain a preinitialised 'phys->machine' translation
> table, and only create initial page tables large enough to contain the
> kernel image, initial page tables, and the translation table. 16MB of
> VA space would be plenty.
VA should probably have the size of text+data+bss. My preferred layout
would be pagetables/pgd/p2m-mapping at the end of the domain's physical
memory in that order. And this should then be either mapped at VA 0, end
aligned with text or end aligned with the hypervisor memory. I think I'd
choose end aligned with the hypervisor memory.
> As for breaking the interface to other types of guest OS
> (ie. non-Linux) -- they can implement their own domain builder that
> sets memory out just as they like.
How's that supposed to work for non-Linux domain0 guests?
christian
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-24 12:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 22:37 Xen at scale MAGENHEIMER,DAN (HP-FtCollins,ex1)
2004-03-23 22:59 ` Alex Ho
2004-03-23 23:08 ` Ian Pratt
2004-03-23 23:23 ` Christian Limpach
2004-03-24 6:54 ` Kip Macy
2004-03-24 10:31 ` Christian Limpach
2004-03-24 10:49 ` Keir Fraser
2004-03-24 12:12 ` Christian Limpach [this message]
2004-03-24 15:56 ` Kip Macy
2004-03-24 17:15 ` Christian Limpach
2004-03-24 18:39 ` Kip Macy
2004-03-24 19:41 ` Christian Limpach
2004-03-24 19:55 ` Kip Macy
2004-03-24 21:06 ` xen-1.2 again I RATTAN
2004-03-24 21:22 ` Ian Pratt
2004-03-24 21:41 ` I RATTAN
-- strict thread matches above, loose matches on Subject: below --
2004-03-23 23:47 Xen at scale MAGENHEIMER,DAN (HP-FtCollins,ex1)
[not found] <becker@cs.duke.edu>
2004-03-18 15:44 ` David Becker
2004-03-18 16:00 ` Ian Pratt
2004-03-18 16:27 ` David Becker
2004-03-18 16:21 ` Mark Williamson
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='0b4e01c41199$3c84a150$070414ac@pin' \
--to=chris@pin.lu \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=dan.magenheimer@hp.com \
--cc=kmacy@fsmware.com \
--cc=xen-devel@lists.sourceforge.net \
/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.