From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: david.vrabel@citrix.com, Ian.Campbell@citrix.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim.Deegan@citrix.com
Subject: [PATCH 01/11] arm: few missing #define
Date: Thu, 2 Feb 2012 16:38:00 +0000 [thread overview]
Message-ID: <1328200690-26454-1-git-send-email-stefano.stabellini@eu.citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1202021536090.3196@kaball-desktop>
Few missing #define are the cause of a compile failure with
XEN_TARGET_ARM=arm and XEN_COMPILE_ARM=arm (for example in the case of a
native compilation). This patch fill the gaps.
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
---
xen/include/public/arch-arm.h | 2 ++
xen/include/public/io/protocols.h | 3 +++
2 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/xen/include/public/arch-arm.h b/xen/include/public/arch-arm.h
index c430cf3..e04c4fd 100644
--- a/xen/include/public/arch-arm.h
+++ b/xen/include/public/arch-arm.h
@@ -110,6 +110,8 @@ typedef struct arch_vcpu_info arch_vcpu_info_t;
struct arch_shared_info { };
typedef struct arch_shared_info arch_shared_info_t;
+typedef unsigned long xen_callback_t;
+
#endif
#endif /* __XEN_PUBLIC_ARCH_ARM_H__ */
diff --git a/xen/include/public/io/protocols.h b/xen/include/public/io/protocols.h
index 77bd1bd..0b7a2ea 100644
--- a/xen/include/public/io/protocols.h
+++ b/xen/include/public/io/protocols.h
@@ -26,6 +26,7 @@
#define XEN_IO_PROTO_ABI_X86_32 "x86_32-abi"
#define XEN_IO_PROTO_ABI_X86_64 "x86_64-abi"
#define XEN_IO_PROTO_ABI_IA64 "ia64-abi"
+#define XEN_IO_PROTO_ABI_ARM "arm-abi"
#if defined(__i386__)
# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_X86_32
@@ -33,6 +34,8 @@
# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_X86_64
#elif defined(__ia64__)
# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_IA64
+#elif defined(__arm__)
+# define XEN_IO_PROTO_ABI_NATIVE XEN_IO_PROTO_ABI_ARM
#else
# error arch fixup needed here
#endif
--
1.7.8.3
next prev parent reply other threads:[~2012-02-02 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 16:37 [PATCH 00/11] arm: compile tools Stefano Stabellini
2012-02-02 16:38 ` Stefano Stabellini [this message]
2012-02-02 16:41 ` [PATCH 01/11] arm: few missing #define Tim Deegan
2012-02-02 16:44 ` Ian Campbell
2012-02-02 16:38 ` [PATCH 02/11] arm: add stub hvm/save.h Stefano Stabellini
2012-02-02 16:38 ` [PATCH 03/11] arm: arch_dump_shared_mem_info as a no-op Stefano Stabellini
2012-02-02 16:38 ` [PATCH 04/11] libxl: do not allocate e820 for non x86 guests Stefano Stabellini
2012-02-02 16:38 ` [PATCH 05/11] blktap2/libvhd: Build shared objects using -fPIC Stefano Stabellini
2012-02-02 16:38 ` [PATCH 06/11] arm: compile libxc Stefano Stabellini
2012-02-02 16:38 ` [PATCH 07/11] arm: compile libxenguest Stefano Stabellini
2012-02-02 16:38 ` [PATCH 08/11] arm: compile libxl Stefano Stabellini
2012-02-02 16:38 ` [PATCH 09/11] arm: compile memshr Stefano Stabellini
2012-02-02 16:38 ` [PATCH 10/11] arm: compile xentrace Stefano Stabellini
2012-02-02 16:38 ` [PATCH 11/11] tools: only compile libfsimage/xfs on X86 Stefano Stabellini
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=1328200690-26454-1-git-send-email-stefano.stabellini@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Tim.Deegan@citrix.com \
--cc=david.vrabel@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).