> How about you just check cpu_core_map[] instead of adding your
> own custom detection code for this? This seems quite bogus to me.
Because these <whatever>map[]s are poorly documented, change
(get added or removed), and don't always exist in all subarchs.
I've been burned by cpu-related maps changing before. I'd rather
not rely on them if I can avoid them.
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]