Per-cpu patches on top of PDA stuff...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 20, 2006 at 02:10:31PM -0400, James Bottomley wrote:
> On Wed, 2006-09-20 at 19:49 +0200, Andi Kleen wrote:
> > Because it makes it easier to write other code? We don't really
> > want any unnecessary limiting assumptions in arch/i386 just because
> > of some obscure machine with one user.
> 
> Really?  I don't see it that way.  I did a lot of work back in 2000/2001
> to break x86 of its remapped CPU assumptions ... it's been operating
> nicely for 6 years, I don't see a reason to break it now.

There are already CPU #0 assumptions in various paths, although
they might not affect you.

> 
> Also, as we enter the era of hotplug CPUs, when a non voyager x86 system
> tells you CPU3 is overheating, how to you find out exactly which CPU to
> hot unplug?

Right now you can't anyways, but at some point I would expect this
information to be in the SMBIOS (mapped from APIC-ID) and giving
some label that is printed on the motherboard.

We already support this for DIMMs BTW (although it doesn't work
everywhere due to very creative spec interpretation of some vendors) 

-Andi


[Index of Archives]     [KVM Development]     [Libvirt Development]     [Libvirt Users]     [CentOS Virtualization]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux