From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Use of XEN_GUEST_HANDLE
Date: Sat, 24 May 2008 23:23:18 +0100
Message-ID: <48389556.7020908@goop.org>
References: <17357081.post@talk.nabble.com>
	<200805242310.44450.mark.williamson@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <200805242310.44450.mark.williamson@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, sandesh <sandesh.ahiremath@wipro.com>
List-Id: xen-devel@lists.xenproject.org

Mark Williamson wrote:
> The guest handle abstraction was put in place to allow PPC (and potentially 
> other) ports to implement a different way of addressing structures that 
> assumed less x86-like architecture behaviour.
>   

ia64 is a current user of this stuff.  They just put it all back into 
paravirt-ops...

    J