From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [PATCH] Enble 6 argument hypercalls for HVMs Date: Wed, 15 Dec 2010 10:06:16 +0000 Message-ID: References: <4D08936B02000078000280D3@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4D08936B02000078000280D3@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Ross Philipson Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 15/12/2010 09:07, "Jan Beulich" wrote: >>>> On 14.12.10 at 23:16, Ross Philipson wrote: >> Enable 6 argument hypercalls for HVMs. The hypercall code handles a sixth >> argument in EBP or R9 but the HVM code is not passing the value. >> >> Signed-off-by: Ross Philipson > > I'm curious what hypercall there is that takes 6 arguments, > particularly on 64-bit (where the maximum so far is 4). The v4v hypercalls in XenClient (not as yet submitted upstream) take 6 arguments. Multicalls also need fixing up for a sixth argument, making everything consistent with existing PV hypercall logic. -- Keir > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel