On Thu, 5 Sep 2013, Catalin Marinas wrote:
On Thu, Aug 29, 2013 at 07:32:26PM +0100, Stefano Stabellini wrote:
quoted
Move Xen initialization earlier, before any DMA requests can be made.
Signed-off-by: Stefano Stabellini <redacted>
I guess you should cc the corresponding maintainers here.
Thanks for the reminder, I'll do that.
quoted
arch/arm/include/asm/xen/hypervisor.h | 8 ++++++++
arch/arm/kernel/setup.c | 2 ++
arch/arm/xen/enlighten.c | 21 ++++++++++++++-------
arch/arm64/kernel/setup.c | 2 ++
4 files changed, 26 insertions(+), 7 deletions(-)
[...]
quoted
--- a/arch/arm64/kernel/setup.c
+++ b/arch/arm64/kernel/setup.c
@@ -53,6 +53,7 @@
#include <asm/traps.h>
#include <asm/memblock.h>
#include <asm/psci.h>
+#include <asm/xen/hypervisor.h>
unsigned int processor_id;
EXPORT_SYMBOL(processor_id);
@@ -267,6 +268,7 @@ void __init setup_arch(char **cmdline_p)
unflatten_device_tree();
psci_init();
+ xen_early_init();
So Xen guests don't have any hope for single Image? Basically you set
dma_ops unconditionally in xen_early_init(), even if the kernel is not
intended to run under Xen.
That should not happen: if we are not running on Xen xen_early_init
returns early, before calling xen_mm_init.