From: Christian Limpach <chris@pin.lu>
To: Kip Macy <kmacy@fsmware.com>
Cc: "MAGENHEIMER,DAN (HP-FtCollins,ex1)" <dan.magenheimer@hp.com>,
xen-devel@lists.sourceforge.net
Subject: Re: Xen at scale
Date: Wed, 24 Mar 2004 11:31:29 +0100 [thread overview]
Message-ID: <0aee01c4118b$2c1beb10$070414ac@pin> (raw)
In-Reply-To: 20040323222107.A37635@demos.bsdclusters.com
> The {DragonFly/Free}BSD domain builder sets the page tables up a little
> differently. It populates the phys_to_machine array before starting
> the domain - mapping it at a pre-determined address relative to
> KERNBASE.
How is it pre-determined?
And where do you put it physically? I would probably put it at the very end
of the physical address space since the guest is less likely to rebuild the
mapping table than it is likely to rebuild the pagetables. Every other
place seems to require special handling in the guests memory management...
Having a domain layout which isn't compatible with the Linux one is a
problem if you want to boot your domain as domain0 since the builder for
domain0 is inside Xen.
> > Maybe there's a simpler solution?
>
> I don't think passing an array is more complicated.
It's more complicated because you need to put it somewhere and then most
guests have to possibly move it around because they don't like where it was
put by the builder. But most of all I think that it's a bad idea to use two
different interfaces to pass the same kind of data and that we should try to
keep the amount of pre-initialized data to a minimum.
It might still be time to switch to using an array but the sooner the better
and then we should stick with whatever we choose...
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 10:31 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 [this message]
2004-03-24 10:49 ` Keir Fraser
2004-03-24 12:12 ` Christian Limpach
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='0aee01c4118b$2c1beb10$070414ac@pin' \
--to=chris@pin.lu \
--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.