From: David Vrabel <david.vrabel@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Jan Beulich <JBeulich@suse.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH 1/2] xen: event channel arrays are xen_ulong_t and not unsigned long
Date: Fri, 15 Feb 2013 13:54:44 +0000 [thread overview]
Message-ID: <511E3E24.2040202@citrix.com> (raw)
In-Reply-To: <1360851590-2539-1-git-send-email-ian.campbell@citrix.com>
On 14/02/13 14:19, Ian Campbell wrote:
> On ARM we want these to be the same size on 32- and 64-bit.
>
> This is an ABI change on ARM. X86 does not change.
Does this actually work for all possible events? In a 32-bit guest on a
64-bit hypervisor, does the __ffs() find set bits in the upper 32-bit
word of the pending selector? I don't think so.
David
next prev parent reply other threads:[~2013-02-15 13:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 14:16 [PATCH 00/NN] linux: public interface changes for arm Ian Campbell
2013-02-14 14:19 ` [PATCH 1/2] xen: event channel arrays are xen_ulong_t and not unsigned long Ian Campbell
2013-02-15 12:22 ` Stefano Stabellini
2013-02-15 14:03 ` Ian Campbell
2013-02-15 13:54 ` David Vrabel [this message]
2013-02-14 14:19 ` [PATCH 2/2] xen: make start_info x86 specific Ian Campbell
2013-02-15 12:08 ` Stefano Stabellini
2013-02-15 13:01 ` Jan Beulich
2013-02-15 13:24 ` Ian Campbell
2013-02-15 13:41 ` Jan Beulich
2013-02-15 14:06 ` Ian Campbell
2013-02-15 14:55 ` Jan Beulich
2013-02-14 14:20 ` [PATCH 00/NN] linux: public interface changes for arm Ian Campbell
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=511E3E24.2040202@citrix.com \
--to=david.vrabel@citrix.com \
--cc=JBeulich@suse.com \
--cc=ian.campbell@citrix.com \
--cc=keir@xen.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.