From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com,
shaohua.li@intel.com, ashok.raj@intel.com
Subject: Re: [Patch] x86: fix smp_num_siblings on buggy BIOSes
Date: Thu, 26 May 2005 23:36:59 -0700 [thread overview]
Message-ID: <20050526233658.A28476@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050526221737.7fc42984.akpm@osdl.org>; from akpm@osdl.org on Thu, May 26, 2005 at 10:17:37PM -0700
On Thu, May 26, 2005 at 10:17:37PM -0700, Andrew Morton wrote:
> "Siddha, Suresh B" <suresh.b.siddha@intel.com> wrote:
> >
> > Appended patch will fix 'smp_num_siblings' value on the systems with
> > buggy bios, which sets number of siblings to '2' even when HT is disabled.
> > (more details are at http://bugzilla.kernel.org/show_bug.cgi?id=4359)
> >
> > I am planning to do more cleanup in this area (like moving smp_num_siblings
> > to per cpuinfo) shortly.
> >
> > But meanwhile, please pickup this patch for 2.6.12.
> >
> > Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
> > Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> >
> > --- linux-2.6.12-rc5/arch/i386/kernel/smpboot.c~ 2005-05-25 16:47:56.462416368 -0700
> > +++ linux-2.6.12-rc5/arch/i386/kernel/smpboot.c 2005-05-25 16:48:14.556665624 -0700
> > @@ -1074,8 +1074,10 @@
> > cpu_set(cpu, cpu_sibling_map[cpu]);
> > }
> >
> > - if (siblings != smp_num_siblings)
> > + if (siblings != smp_num_siblings) {
> > printk(KERN_WARNING "WARNING: %d siblings found for CPU%d, should be %d\n", siblings, cpu, smp_num_siblings);
> > + smp_num_siblings = siblings;
> > + }
> >
> > if (c->x86_num_cores > 1) {
> > for (i = 0; i < NR_CPUS; i++) {
>
> OK, but be aware that -mm's sibling-map-initializing-rework.patch
> cheerfully deletes all the surrounding code. So -mm will not have this
> fix.
>
> There's a completely loony amount of x86 stuff in -mm.
Thanks for this info. I will send a fix for -mm also.
BTW, when do you plan to integrate x86 cpu hotplug patches to mainline?
Depending on that I will plan my "smp_num_siblings" global cleanup.
thanks,
suresh
next parent reply other threads:[~2005-05-27 6:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050525173456.A11038@unix-os.sc.intel.com>
[not found] ` <20050526221737.7fc42984.akpm@osdl.org>
2005-05-27 6:36 ` Siddha, Suresh B [this message]
2005-05-27 7:02 ` Andrew Morton
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=20050526233658.A28476@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=venkatesh.pallipadi@intel.com \
/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®