From: Andi Kleen <ak@muc.de>
To: Ashok Raj <ashok.raj@intel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 09/14] x86_64: Don't call enforce_max_cpus when hotplug is enabled
Date: 7 Sep 2005 08:49:50 +0200 [thread overview]
Date: Wed, 7 Sep 2005 08:49:50 +0200 [thread overview]
Message-ID: <20050907064950.GB96684@muc.de> (raw)
In-Reply-To: <20050906155617.A19439@unix-os.sc.intel.com>
On Tue, Sep 06, 2005 at 03:56:17PM -0700, Ashok Raj wrote:
> Hi Andi
>
> On Mon, Sep 05, 2005 at 06:48:21AM +0200, Andi Kleen wrote:
> > On Sat, Sep 03, 2005 at 02:33:26PM -0700, akpm@osdl.org wrote:
> > >
> > > From: Ashok Raj <ashok.raj@intel.com>
> > >
> > > No need to enforce_max_cpus when hotplug code is enabled. This nukes out
> > > cpu_present_map and cpu_possible_map making it impossible to add new cpus in
> > > the system.
> >
> > I see the point, but the implementation is wrong. If anything
> > we shouldn't do it neither for the !HOTPLUG_CPU case.Why did
> > you not do it unconditionally?
> >
> > I would prefer to keep the special cases for hotplug to be
> > as narrow as possible.
>
> Link to earlier discussion below
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=112317327529855&w=2
>
> I had suggested that we remove it completely in our discussion but i didnt
> hear anything from you after that, so i thought that was acceptable.
Just because I don't follow up on everything doesn't necessarily
mean the patch is acceptable.
>
> You had suggested in that discussion that it would be better to add an
> option for startup. Iam opposed to adding any option, when we certainly know
I suggested to auto detect it based on ACPI information. I don't
think I ever wrote anything about an option.
If that is not possible it's better to always use the sequence mechanism.
> there are no users. Earlier based on your suggestion i added a startup
> option to choose ipi broadcast mode, which you promptly removed when you
> put physflat changes. I think its better to not add any option without
> real need. Do you agree?
Yes.
> Please reply if you want me to remove the !HOTPLUG case which is my
> preference as well, and maybe while the memory is fresh, we can stick
> with it this time when we are in the same page :-(
Yes, as I wrote earlier hotplug should be removed.
-Andi
P.S.: Don't bother sending me such "blame game" mails again. I will
just d them next time because they're a waste of time.
next prev parent reply other threads:[~2005-09-07 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509032135.j83LZ5Od020541@shell0.pdx.osdl.net>
[not found] ` <20050905044821.GH17516@muc.de>
2005-09-06 22:56 ` Ashok Raj
2005-09-07 6:49 ` Andi Kleen [this message]
2005-09-07 16:27 ` Ashok Raj
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=20050907064950.GB96684@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®