[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] Allow direct hypercalls


  • To: <john.levon@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Thu, 01 May 2008 16:03:43 +0100
  • Delivery-date: Thu, 01 May 2008 08:56:50 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcirnIvfyoHEgRePEd2RRAAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH] Allow direct hypercalls

On 30/4/08 13:56, "john.levon@xxxxxxx" <john.levon@xxxxxxx> wrote:

> # HG changeset patch
> # User john.levon@xxxxxxx
> # Date 1209521783 25200
> # Node ID 9a5c6e3620d83f9354e3eedbc4ef24a7a5ad752e
> # Parent  f477f895f78752bb9fa2e6ee6c1d09b6a8cd3230
> Allow direct hypercalls
> 
> For PV guests, there's no reason to force use of the indirect hypercall
> mechanism. Allow it. Also allow TRAP_INSTR to be used from assembly.
> 
> Signed-off-by: John Levon <john.levon@xxxxxxx>

Well, I suppose there is no reason. But since the instructions are not going
to change you could just as well just open-code them, or define your own
macro. _ASM isn't even a macro name that we use anywhere else in the public
headers.

 -- Keir



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.