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

Re: [Xen-ia64-devel] domU address space

To: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Subject: Re: [Xen-ia64-devel] domU address space
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Thu, 24 Jan 2008 11:29:11 +0900
Cc: xen-ia64-devel <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 23 Jan 2008 18:29:55 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <10EA09EFD8728347A513008B6B0DA77A02AF18C3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <10EA09EFD8728347A513008B6B0DA77A02AF18C3@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Thu, Jan 24, 2008 at 09:28:39AM +0800, Dong, Eddie wrote:
> Alex & All:
>       First of all, pls forgive me that I was out of Xen/IA64 for quit
> a long time, and I didn't fully catch up yet now.
>       In the very beginning day of Xen/IA64, I remembered the address
> isolation between guest (domU) & hypervisor is not solved though guest
> PAL can provide less number of VA bits, it just assume pv guest won't
> touch hypervisor address space, i.e. it will strictly follow PAL
> reported VA address bits. Is this solved now?

Yes. (Possibly there might be bugs, though.)
In paravirtualized domain case, PV domain is running under
ring 2 (or ring 1 depending on the compile time configuration), and
the xen area is proteceted by privileged level.
In VTi domain case, it's protected by psr.vm = 1.

-- 
yamahata

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