Messages in this thread | | | Date | Thu, 19 Sep 2002 21:09:05 -0700 | From | William Lee Irwin III <> | Subject | Re: [BUG] x86_udelay_tsc not honoring notsc |
| |
At some point in the past, I wrote: >> If so, it's probably not worth mucking around with the bootstrap >> sequence to deal with something this minor. It's not like it can >> be mistaken for having hung, as console output is very consistent. >> Maybe we should give NUMA-Q a couple of minutes instead of 5s?
On Thu, Sep 19, 2002 at 09:00:09PM -0700, Martin J. Bligh wrote: > Nah, just recode the boot sequence to make them all boot in > parallel ;-) > M.
Do you think cpu wakeup alone could be doing this? If so, then doing that bit would be relatively isolated (though a slightly larger diff than changing an NMI oopser timeout).
Does 0xFF broadcast cluster, broadcast low nybble work or is waking them a cluster at a time required? This thing is not swift to boot...
Thanks, Bill - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |