Re: [BISECTION RESULT] sched: revert cpu_clock topre-27ec4407790d075c325e1f4da0a19c56953cce23 state

[David Miller]

From: "Luck, Tony" <tony.luck@xxxxxxxxx>
Date: Mon, 4 Aug 2008 15:00:47 -0700

> > I'd bet resonable sums of money that we are (once again) accessing
> > per-cpu variables in code before ia64 has a chance to initialize
> > things so that they can actually work. :-(
> 
> I tried this simple hack to check ... per-cpu variables are
> not usable until cpu_init() sets up the "ar.k3" register on
> ia64.  So this hack checks to see if it is set before calling
> cpu_clock():

Can you guys on IA64 possibly set ar.k3 simply to zero or to some
other similar value which cancels out the per-cpu computation?

That's what sparc64 and other platforms do.
--
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/