Hi,
On Tue, 2007-11-27 at 09:00 -0800, Jeremy Fitzhardinge wrote:
> > Why do you think that's a CR0 write?
>
> Well, the oops says "EIP is at native_write_cr0+0x0/0x4", and the caller
> is prepare_set(), which does:
>
> /* Enter the no-fill (CD=1, NW=0) cache mode and flush caches. */
> cr0 = read_cr0() | X86_CR0_CD;
> write_cr0(cr0);
> wbinvd();
>
> This is in preparation to setting up the MTRRs,
Right: cpu 0 gets past the early mtrr init (on the boot CPU, all the
kernel does is to probe the existing mtrr config), but it dies on cpu 1
trying to copy the mtrr config across. (As a consequence, we don't hit
this problem on UP configs.)
> which needs to be all skipped anyway.
We _could_ just skip it, but we still want some mtrr support for dom0.
Fortunately the kernel's mtrr interfaces are nicely modular already, so
I'm currently starting to plug the 2.6.18 mtrr/main-xen.c into pv_ops as
a modular mtrr provider.
> > The messages clearly indicate an
> > MSR write, and these writes are clearly visible in
> > intel_p{4,6}_mcheck_init()
> > and amd_mcheck_init(). The question is why intel_p4_mcheck_init() doesn't
> > check CPUID bits before trying to touch any registers... (And similarly
> > amd_mcheck_init() is checking only the MCE bit, not the MCA one.)
> The oops and backtrace doesn't suggest it's an MSR write. Does a crX
> write take the same path through the emulator as an MSR write?
We get a slew of MCE-related MSR write warnings from the HV on both boot
and auxiliary processor bring-up, but the kernel doesn't crash at those
points. (Which is not necessarily a good thing, as it implies the
kernel thinks it has registered its MCE handling, but the MSR writes
have not actually been honoured.) So it's not a showstopper right now,
but is something we'll still want to deal with at some stage.
> > A simple workaround would be to force mce_disabled to 1 in early Xen
> > initialization.
> That's probably necessary too.
It doesn't seem to be necessary, given that the kernel does get past
this point; it's probably desirable, though, at least until such time as
we can actually do the MCE support correctly.
--Stephen
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home