Re: [PATCH] DevFS support for /dev/cpu/X/(cpuid|msr)

[H. Peter Anvin]

Richard Gooch wrote:

>>>
>>If you don't understand why this is idiotic, then let me enlighten you: 
>>there is no sensible reason why /dev/cpu/%d should only be populated 
>>after having run a CPU-dependent device driver.  /dev/cpu/%d should be 
>>always populated; heck, that's the only way you can sensibly handle 
>>hotswapping CPUs.
> 
> I've already privately told Matt that it would be nice if creation of
> /dev/cpu/%d was handled by generic boot code, and not a driver.
> However, I don't see that as essential for the CPUID and MSR drivers.
> 

I don't see putting a lot of devfs shit into the CPUID and MSR drivers 
as essential in any shape, way or form.  Do it right or don't do it at all.

	-hpa