On Fri, Aug 03, 2012 at 12:09:15PM +0200, Kay Sievers wrote: > That would be needed, I guess. We easily have server systems with more > than 255 CPUs. It will only be a matter of time, that the number of > CPUs will increase for everybody, I guess.
Actually, AFAICR, we already have SGI machines booting Linux on 4K cpus. Now. > > b) to put cpuid in struct cont and struct log - under the #ifdef macro? > > As said, I really can't tell how generally useful it is, and if people > think that it should be there unconditionally, should not be there at > all, or as a compile time option. Others might have an opinion on > that. > > I personally never missed the CPU-ID in the logs. I personally would > find the PID/task ID more interesting, and even that I never really > missed. :) And even then you can add debugging code to dump the stuff you need. And I have to agree with Kai here, having the cpu number in dmesg is not something I'd wish for - printk timestampts OTOH has at least some usecases. Thanks. -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
