> What I'm suggesting is to very early on set ar.k3 to something which > makes accesses go through the __per_cpu image copy in the main kernel > image. I'm looking at that ... but it is a bit more complex. We only have a "__per_cpu" block in the kernel on uni-processor systems. For larger systems we dynamically allocate, and we have two different mechanisms to that (one for SMP and one for NUMA). > You could even set up a dummy TLB mapping during this early boot > period. Also a plausible idea ... though I'm not sure which physical address I'd point this mapping at given the above allocation techniques. Some of the problem here is that the kernel makes printk() calls before any architecture dependent C code gets run. > Otherwise it's just cleverness that is unique to IA64 and is going to > constantly run into issues like this. An alternative is to implement > your own sched_clock() et al. where you can adhere to whatever special > rules your platform may have. Sigh. we used to have our own (added by akpm in 2005) until it got deleted :-( -Tony -- To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|