On Thu, Aug 29, 2013 at 07:32:26PM +0100, Stefano Stabellini wrote: > Move Xen initialization earlier, before any DMA requests can be made. > > Signed-off-by: Stefano Stabellini <stefano.stabell...@eu.citrix.com>
I guess you should cc the corresponding maintainers here. > 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(-) [...] > --- 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. -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
