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: [PATCH] Linux: 6 arguments hypercall v2

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH] Linux: 6 arguments hypercall v2
From: Jean Guyader <jean.guyader@xxxxxxxxxxxxx>
Date: Fri, 24 Jun 2011 15:59:01 +0100
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jean Guyader <Jean.Guyader@xxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Fri, 24 Jun 2011 08:06:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1308926818.32717.135.camel@xxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20110624140044.GA22264@xxxxxxxxxxxxxxxxxxxxxxx> <1308926818.32717.135.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On 24/06 03:46, Ian Campbell wrote:
> On Fri, 2011-06-24 at 15:00 +0100, Jean Guyader wrote:
> > Hi,
> > 
> > This patch implements the 6 arguments hypercalls.
> > The sixth argument is passed using ebp or r9.
> Looks pretty good.
> I was able to get rid of more of the ifdefery etc with the following. It
> appears to do the right thing (by inspection of compiled code, not
> actual testing).
> Defining both __res and __arg6 as register("eax") seems slightly
> dubious, as is including them both in  __HYPERCALL_6PARAM, but gcc
> doesn't seem to mind and it makes  __HYPERCALL_6PARAM the same in both
> cases and gets rid of __HYPERCALL_DECLS6.
> Your version is probably less likely to tickle ggc bugs/behaviour
> changes in the future, so it's likely safer I think.

Thanks that makes the code much nicer, I didn't really want to declare
to variable in eax but if that works fine.

Also my patch modifies  HYPERVISOR_set_trap_table by mistake but
shouldn't. I only used that for testing _hypercall6. I'll send
another version with your changes in but without the mistake
at the end.


Xen-devel mailing list

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