Re: [Xen-devel] Re: [PATCH 00 of 36] x86/paravirt: groundwork for64-bit Xen support
From: Jeremy Fitzhardinge
Date: Thu Jul 03 2008 - 11:47:53 EST
Ingo Molnar wrote:
* Ingo Molnar <mingo@xxxxxxx> wrote:
* Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:
Ingo Molnar wrote:
Excluding the x86/xen-64bit topic solves the problem.
It triggered on two 64-bit machines so it seems readily reproducible
with that config.
i've pushed the failing tree out to tip/tmp.xen-64bit.Tue_Jul__1_10_55
The patch to fix this is on tip/x86/unify-setup: "x86: setup_arch() &&
early_ioremap_init()". Logically that patch should probably be in the
xen64 branch, since it's only meaningful with the early_ioremap
unification.
ah, indeed - it was missing from tip/master due to:
| commit ac998c259605741efcfbd215533b379970ba1d9f
| Author: Ingo Molnar <mingo@xxxxxxx>
| Date: Mon Jun 30 12:01:31 2008 +0200
|
| Revert "x86: setup_arch() && early_ioremap_init()"
|
| This reverts commit 181b3601a1a7d2ac3ace6b23cb3204450a4f9a27.
because that change needed the other changes from xen-64bit.
will retry tomorrow.
ok, i've re-added x86/xen-64bit and it's looking good in testing so far.
Great. I'm hoping this stuff will be OK for the next merge, so I'm
primed for fast turnaround bugfixes ;)
Also, I have the series of followup patches to actually implement 64-bit
Xen which have much less impact on the non-Xen parts of the tree. I'll
probably mail them out later today.
Thanks,
J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/