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

[Xen-ia64-devel] cpu ops

To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-ia64-devel] cpu ops
From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
Date: Mon, 7 Apr 2008 17:25:54 +0800
Delivery-date: Mon, 07 Apr 2008 02:32:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AciYkWEppDUyD7AqTvOsRtHE9O/zKA==
Thread-topic: cpu ops
In current approach, we have cpu ops like eoi/set_tpr/get_tpr,/set_itm
/set_kr0/set_kr2.../set_kr7 etc.
I think there is another simple alternative is to simply export
setreg/getreg 
for cpu ops.

The benefit of this could be:
        1: Simple in pv_ops I/F
        2: hypervisor neutral. Today we only virtualize around 15 AR/CR
read/write,
        But future it may extends since different Hypervisor may do in
different way.

Do u like to see this one happen?
thanks, eddie

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

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