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

[Xen-devel] [Q] guest and user protection on x86-64 by paging

To: Xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [Q] guest and user protection on x86-64 by paging
From: Min Lee <min.lee@xxxxxxxxxx>
Date: Sun, 01 Aug 2010 12:01:14 -0400
Cc:
Delivery-date: Sun, 01 Aug 2010 09:02:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.7) Gecko/20100713 Thunderbird/3.1.1
Hi, folks.
one question. I'll read source code, but if one can give me brief overview, it would be so helpful. On x86-64, guest and user runs both in ring 3, and protect from each other by paging mechanism. but, how? Then page table should be modified and TLB would be flushed for every system call. This would be some overhead, I think. Is this what Xen is doing? If not, how paging mechanism protect guest from its application?
Thanks
Min

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

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