From: Andi Kleen <ak@muc.de>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Morton <akpm@osdl.org>,
virtualization@lists.osdl.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: Per-cpu patches on top of PDA stuff...
Date: 20 Sep 2006 20:42:09 +0200
Date: Wed, 20 Sep 2006 20:42:09 +0200 [thread overview]
Message-ID: <20060920184209.GA61408@muc.de> (raw)
In-Reply-To: <1158775832.9633.115.camel@mulgrave.il.steeleye.com>
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
next prev parent reply other threads:[~2006-09-20 18:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 3:13 Per-cpu patches on top of PDA stuff Rusty Russell
2006-09-19 8:03 ` Rusty Russell
2006-09-19 8:26 ` Andi Kleen
2006-09-19 20:39 ` Jeremy Fitzhardinge
2006-09-19 8:14 ` Jeremy Fitzhardinge
2006-09-19 21:03 ` Chris Wright
2006-09-19 22:36 ` Jeremy Fitzhardinge
2006-09-20 0:07 ` Rusty Russell
2006-09-20 7:00 ` Andi Kleen
2006-09-20 12:54 ` James Bottomley
2006-09-20 16:09 ` Andi Kleen
2006-09-20 16:15 ` James Bottomley
2006-09-20 16:22 ` Andi Kleen
2006-09-20 16:42 ` James Bottomley
2006-09-20 17:49 ` Andi Kleen
2006-09-20 18:10 ` James Bottomley
2006-09-20 18:42 ` Andi Kleen [this message]
2006-09-21 8:54 ` Rusty Russell
2006-09-19 20:37 ` Chris Wright
2006-09-19 20:40 ` Jeremy Fitzhardinge
2006-09-19 21:08 ` Chris Wright
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060920184209.GA61408@muc.de \
--to=ak@muc.de \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=mingo@elte.hu \
--cc=virtualization@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.