On Thu, 2 Jun 2005, Keir Fraser wrote:
> On 2 Jun 2005, at 22:09, Carl Holtje ;021;vcsg6; wrote:
> > Ok.. so I've 'upgraded' to using the xen-unstable tree... and walked
> > into
> > a bunch more trouble..
> > I'm totally lost looking at the assembler for
> > xen/arch/x86/string.c#memset, but that seems to be where my latest
> > "unknown interrupt" message is coming from (originating from
> > xen/arch/x86/mm.c#init_frametable)... how do I go about fixing
> > this?
> > I moved the init_trap() call in setup.c before this, but don't get
> > anything.. must be too early?
> > Thanks again... your help is definitely appreciated!
> Let's take a step back: does the CPU have all the capabilities that Xen
> expects? If you run 'cat /proc/cpuinfo' on native Linux, do you see all
> the following flags: fpu, pse, tsc, cx8, pge?
> Those are the ones I'm pretty sure you'll run into trouble if you lack.
> If you have all those then we should press on and find the bugs. :-)
The only one I don't have is PGE -- but this should be a performance
thing, not so much a functionality issue, right?
(Here's the appropriate substring from /proc/cpuinfo: fpu vme de pse tsc
msr cx8 sep cmov mmx pni longrun lrt)
"There are 10 types of people in the world: Those who understand binary
and those that don't."
Xen-devel mailing list