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] Re: [Xen-changelog] Indirect hypercalls through a hypercall

To: Hollis Blanchard <hollisb@xxxxxxxxxx>
Subject: [Xen-devel] Re: [Xen-changelog] Indirect hypercalls through a hypercall transfer page.
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 8 Feb 2006 08:46:13 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 08 Feb 2006 08:58:13 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1139374660.11984.30.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <E1F1lA0-0001fQ-Mv@xxxxxxxxxxxxxxxxxxxxx> <1139374660.11984.30.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 8 Feb 2006, at 04:57, Hollis Blanchard wrote:

Indirect hypercalls through a hypercall transfer page.

Sorry, I may have missed some conversation about this...

What is this patch about? I mean I can see how it works, but what is the
motivation for it?

Allows a different hypercall implementation on platforms where that makes sense. For example, we would like to run XenLinux on native by running it over a small 'Xen shim' that provides the Xen API but no protection or multiplexing. In that case it would be most efficient to turn syscall instructions into jumps.

 -- Keir

Xen-devel mailing list

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