From: James Bottomley <James.Bottomley@SteelEye.com>
To: Andi Kleen <ak@muc.de>
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: Wed, 20 Sep 2006 12:42:17 -0400 [thread overview]
Message-ID: <1158770537.9633.82.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <200609201822.13488.ak@muc.de>
On Wed, 2006-09-20 at 18:22 +0200, Andi Kleen wrote:
> Well that's your problem then. Just add the remapping array.
I don't see why I should be the one to add unnecessary obfuscation.
Using the current ID scheme, the user always knows exactly where to find
CPU<n> in the chassis (and they are separately installable and
removable). Why should I make up a new identity scheme that would have
no relation to the hardware?
James
next prev parent reply other threads:[~2006-09-20 16: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 [this message]
2006-09-20 17:49 ` Andi Kleen
2006-09-20 18:10 ` James Bottomley
2006-09-20 18:42 ` Andi Kleen
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=1158770537.9633.82.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=ak@muc.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).