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


Re: [Xen-devel] [PATCH] Hypercalls from HVM guests

To: Steve Ofsthun <sofsthun@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Hypercalls from HVM guests
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 22 Apr 2006 09:49:53 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 22 Apr 2006 01:53:48 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <444920C7.2070705@xxxxxxxxxxxxxxx>
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: <444920C7.2070705@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 21 Apr 2006, at 19:13, Steve Ofsthun wrote:

With these changes you can make raw hypercalls from HVM guests.

You probably want a separate hypercall table from that of paravirtualized guests, for several reasons: 1. Some hypercalls will not be HVM aware and are probably unsafe to run from an HVM context 2. Some hypercalls may want different implementations (or at least a wrapper) on HVM 3. On 64-bit, you may even want a separate 32-bit hypercall table containing wrappers that interface between 32-bit callers and the core 64-bit hypercall functions.

(1) is most important right now -- we should only permit the hypercalls we need, and audit any others before they are added to the list.

 -- Keir

Xen-devel mailing list

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