From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: julien.grall@linaro.org, stefano.stabellini@eu.citrix.com,
tim@xen.org, xen-devel@lists.xen.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] arm: xen: implement multicall hypercall support.
Date: Tue, 1 Apr 2014 12:02:22 +0100 [thread overview]
Message-ID: <533A9CBE.9000107@citrix.com> (raw)
In-Reply-To: <1396015660-7834-1-git-send-email-ian.campbell@citrix.com>
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
next prev parent reply other threads:[~2014-04-01 11:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 14:07 [PATCH] xen: arm: fully implement multicall interface Ian Campbell
2014-03-28 14:07 ` [PATCH] arm: xen: implement multicall hypercall support Ian Campbell
2014-03-28 14:51 ` Julien Grall
2014-03-28 14:58 ` Ian Campbell
2014-04-01 11:02 ` David Vrabel [this message]
2014-04-01 11:13 ` Ian Campbell
2014-03-28 14:22 ` [PATCH] xen: arm: fully implement multicall interface Julien Grall
2014-03-28 14:37 ` Ian Campbell
2014-03-28 15:03 ` Jan Beulich
2014-04-01 10:01 ` George Dunlap
2014-03-28 14:45 ` Ian Campbell
2014-03-28 15:01 ` Julien Grall
2014-03-28 15:07 ` Ian Campbell
2014-03-31 16:38 ` George Dunlap
2014-04-01 9:05 ` Julien Grall
2014-04-01 9:28 ` Ian Campbell
2014-04-01 10:46 ` Julien Grall
2014-04-01 10:49 ` Ian Campbell
2014-04-01 11:00 ` Julien Grall
2014-04-01 11:15 ` Ian Campbell
2014-04-01 12:05 ` Julien Grall
2014-04-01 12:11 ` Ian Campbell
2014-04-01 12:16 ` Julien Grall
2014-04-01 12:16 ` Ian Campbell
2014-04-01 12:53 ` Julien Grall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=533A9CBE.9000107@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.