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 07:56:48 -0800 (PST)	[thread overview]
Message-ID: <20040324074648.B68293@demos.bsdclusters.com> (raw)
In-Reply-To: <0b4e01c41199$3c84a150$070414ac@pin>


On FreeBSD i386, there is already a 4MB chunk of VA where the page
tables are mapped - remember that is why the PTD maps itself (as the comment
puts it, recursively). This is the default layout
|  USER         |PTs| KVA     |
  (3GB - 4M)     4M   1GB

I've allocated an extra page-table to the PTOM - for the following VA:

| USER        |PTOM|PTs|  KVA|
  3GB - 8M      4M   4M  1GB

This works well, because all I end up having to do is bump down
VM_MAXUSER_ADDRESS by an extra 4MB. Putting it in the kernel would
disrupt pmap bootstrap. This burns some VA for small memory allocations,
but the same can be said for the PTs and it makes easy for me to put the
PTOM on a single super-page for large memory allocations.

As for DOM0, different guests can have their own setup routines inside Xen.


			-Kip

On Wed, 24 Mar 2004, Christian Limpach wrote:

> > 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
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>


-------------------------------------------------------
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 15:56 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 [this message]
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=20040324074648.B68293@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.