From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org, xen-devel@lists.xenproject.org,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
qemu-arm@nongnu.org
Cc: "Juergen Gross" <jgross@suse.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Anthony Xu" <anthony.xu@intel.com>,
"Anoob Soman" <anoob.soman@citrix.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
xen-arm@lists.xen.org, "Paul Durrant" <paul.durrant@citrix.com>
Subject: [RFC PATCH 2/3] xen/mapcache: disable Xen on arm*
Date: Mon, 10 Jul 2017 23:57:02 -0300 [thread overview]
Message-ID: <20170711025703.24194-3-f4bug@amsat.org> (raw)
In-Reply-To: <20170711025703.24194-1-f4bug@amsat.org>
linking on Linux debian/stretch/arm[64] with libxen-4.8:
exec.o: In function `reclaim_ramblock':
qemu/exec.c:2071: undefined reference to `xen_invalidate_map_cache_entry'
exec.o: In function `qemu_map_ram_ptr':
qemu/exec.c:2177: undefined reference to `xen_map_cache'
qemu/exec.c:2174: undefined reference to `xen_map_cache'
exec.o: In function `qemu_ram_block_from_host':
qemu/exec.c:2242: undefined reference to `xen_ram_addr_from_mapcache'
qemu/exec.c:2242: undefined reference to `xen_ram_addr_from_mapcache'
exec.o: In function `qemu_ram_ptr_length':
qemu/exec.c:2210: undefined reference to `xen_map_cache'
qemu/exec.c:2207: undefined reference to `xen_map_cache'
exec.o: In function `address_space_unmap':
qemu/exec.c:3357: undefined reference to `xen_invalidate_map_cache_entry'
collect2: error: ld returned 1 exit status
Makefile:197: recipe for target 'qemu-system-aarch64' failed
make[1]: *** [qemu-system-aarch64] Error 1
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
---
include/sysemu/xen-mapcache.h | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/include/sysemu/xen-mapcache.h b/include/sysemu/xen-mapcache.h
index 01daaad00c..75f0988e04 100644
--- a/include/sysemu/xen-mapcache.h
+++ b/include/sysemu/xen-mapcache.h
@@ -12,7 +12,9 @@
typedef hwaddr (*phys_offset_to_gaddr_t)(hwaddr start_addr,
ram_addr_t size,
void *opaque);
-#ifdef CONFIG_XEN
+/* FIXME ARM supported since Xen 4.3? */
+#if defined(CONFIG_XEN) /* XXX supported_xen_target() wrong? */ && \
+ !defined(HOST_ARM) && !defined(HOST_AARCH64)
void xen_map_cache_init(phys_offset_to_gaddr_t f,
void *opaque);
--
2.13.2
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-07-11 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 2:57 [RFC PATCH 0/3] disable Xen on ARM (until supported) Philippe Mathieu-Daudé
2017-07-11 2:57 ` [RFC PATCH 1/3] configure: disable Xen PCI Passthrough on !x86 archs Philippe Mathieu-Daudé
2017-07-11 2:57 ` Philippe Mathieu-Daudé [this message]
2017-07-11 2:57 ` [RFC PATCH 3/3] xen/pt: add comments about " Philippe Mathieu-Daudé
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=20170711025703.24194-3-f4bug@amsat.org \
--to=f4bug@amsat.org \
--cc=anoob.soman@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=anthony.xu@intel.com \
--cc=jgross@suse.com \
--cc=mtosatti@redhat.com \
--cc=paul.durrant@citrix.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-arm@lists.xen.org \
--cc=xen-devel@lists.xenproject.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 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).