From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH] arm: xen: implement multicall hypercall support. Date: Tue, 1 Apr 2014 12:02:22 +0100 Message-ID: <533A9CBE.9000107@citrix.com> References: <1396015649-5886-1-git-send-email-ian.campbell@citrix.com> <1396015660-7834-1-git-send-email-ian.campbell@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1396015660-7834-1-git-send-email-ian.campbell@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: julien.grall@linaro.org, stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org, Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org On 28/03/14 14:07, Ian Campbell wrote: > As part of this make the usual change to xen_ulong_t in place of unsigned long. > This change has no impact on x86. > > The Linux defintion of struct multicall_entry.result differs from the Xen > definition, I think for good reasons, and used a long rather than an unsigned > long. Therefore introduce a xen_long_t, which is a long on x86 architectures > and a signed 64-bit integer on ARM. Shouldn't the Xen definition also be changed to use a long? David