WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] question about the meaning of memory auto-translate and

To: tgh <tianguanhua@xxxxxxxxxx>
Subject: Re: [Xen-devel] question about the meaning of memory auto-translate and paravirtual and no pseudophysical overlay
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Wed, 11 Apr 2007 22:28:45 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 11 Apr 2007 14:26:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <461A38A4.80208@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <991B62EB36934C4EBD5B605518A724764C421E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1175962992.12465.11.camel@trevor> <461A38A4.80208@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
> Mark Williamson 写道:
> > This would be a guest that didn't use the abstraction of pseudophysical
> > addresses at all; it would just use virtual and (real) machine
> > addresses.  I'm not sure if there are any guests that operate in this
> > way...  Certainly the major heavyweight OSes all use this technique when
> > paravirtualised.
>
> what is the major heavyweight OSes?

I was referring to the full general purpose OSes that have been ported to Xen, 
i.e.: Linux, NetBSD, Solaris, etc.

> and how does it paravirtualise? 

These all use pseudophysical addresses to maintain the abstraction of a 
vaguely "normal" memory model for their core memory management code to work 
with, then the Xen architecture code in each OS translates these into real 
machine addresses so that everything works properly.

> if there is no pseudophysical addresses,a physical host computer could
> only paravirtualise one VM,is it right?

No, AFAIK pseudophysical addresses are mostly there for the convenience of the 
guest.  Xen has some support for them so that guests can use them more 
efficiently but that's not strictly necessary.  In principle, they could be 
eliminated from Xen entirely (would require modifying the PV guests to manage 
the pseudophys abstraction themselves).

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel