All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@fsmware.com>
To: Christian Limpach <chris@pin.lu>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	"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:55:06 -0800 (PST)	[thread overview]
Message-ID: <20040324114134.G2890@demos.bsdclusters.com> (raw)
In-Reply-To: <0c3201c411d8$028204e0$070414ac@pin>



On Wed, 24 Mar 2004, Christian Limpach wrote:

> > > and where does the builder put the PTD?  and what's the physical memory
> > > layout?
> >
> > For BSD both are irrelevant - the PTD is passed in as an argument via a
> > register. Only Linux relies on physical contiguity for the PTOV trick.
> > BSD does a table lookup in the mapped page tables - it has no physical
> > contiguity requirements.
>
> The domain builder still has to put the PTD somewhere and your
> drawing/explanation doesn't say where.  Same goes for physical memory
> layout, you have to pick one, I'd be interested to know which you picked...

The PTD is an arbitrary physical address mapped in right after the pages
uses by the elf-loader. BSD's VM system is sufficiently general that it
doesn't care about physical layout. Nonetheless, the physical layout
ends up looking something like:

|ktext|KPTphys|IdlePTD|ptomptpa|tmpstk|startinfopa|ptompages| <inited by kernel>

I hadn't intended to commit the domain builder until the ports had been
committed to the BSDs CVS repositories - which is going to wait until
I've had time to write the block and bi-directional console drivers.
However, if it is still unclear I can post the domain builder source
itself.



			-Kip


-------------------------------------------------------
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

  reply	other threads:[~2004-03-24 19:55 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
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 [this message]
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=20040324114134.G2890@demos.bsdclusters.com \
    --to=kmacy@fsmware.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=chris@pin.lu \
    --cc=dan.magenheimer@hp.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.