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/
Home Products Support Community News


[Xen-devel] question about the differences for xen in x86_32 and x86_64

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] question about the differences for xen in x86_32 and x86_64
From: tgh <tianguanhua@xxxxxxxxxx>
Date: Thu, 17 May 2007 16:53:59 +0800
Delivery-date: Thu, 17 May 2007 01:52:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200705170825.l4H8PsrQ009170@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <200705170825.l4H8PsrQ009170@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird (Windows/20060909)
I am confused about the differences betwoon xen in x86_32 and x86_64
in x86_32,Ring 1 for guest OS, ring3 for user-space, Xen lives in top 64MB of linear addr space, Segmentation used to protect Xen as switching page tables too slow on standard x86, Hypercalls jump to Xen in ring 0, Guest OS with ‘fast trap’ handler could direct user-space to guest OS system calls, is it right? while in x86_64 ,both guestos and userapplications seem to run in ring3, and what about other thing memtioned above for x86_64? such as the memory mapping for xen and guestos kernel and applications , system call fast trap handling

I am confused about it
could you help me
Thanks in advance

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>