From: Borislav Petkov <petkovbb@googlemail.com>
To: zhiyi <zhuang@cs.otago.ac.nz>
Cc: linux-kernel@vger.kernel.org, Zhiyi Huang <hzy@cs.otago.ac.nz>,
jkmair@cs.otago.ac.nz
Subject: Re: nr_cpu_ids incorrect on AMD Quad-Core Opteron 8380
Date: Mon, 1 Feb 2010 16:04:42 +0100 [thread overview]
Message-ID: <9ea470501002010704m15dfaedau813b7accfd1d22ff@mail.gmail.com> (raw)
In-Reply-To: <9ea470501002010557o45bad81cp5d9ac3d19318bffe@mail.gmail.com>
On Mon, Feb 1, 2010 at 2:57 PM, Borislav Petkov <petkovbb@googlemail.com> wrote:
> On Sun, Jan 31, 2010 at 11:59 PM, zhiyi <zhuang@cs.otago.ac.nz> wrote:
>> My module worked for a kernel 2.6.29 with CONFIG_NR_CPUS=64 on my dual
>> quad-core AMD Opteron. The value of nr_cpu_ids I got from the same module
>> was correct (8).
>
> This could mean that your include/generated/autoconf.h, which is used by
> external modules, is not updated and contains CONFIG_NR_CPUS=8. Do
>
> make mrproper
>
> in your kernel directory by moving your .config out of the way first and
> then rebuild your kernel and external module(s). nr_cpu_ids should pick
> up the updated CONFIG_NR_CPUS value from your .config.
That's actually not necessary - the nr_cpu_ids thing is set at compile
time to CONFIG_NR_CPUS but then capped to a possibly lower value upon
boot depending on the info in the ACPI mptables. Can you please send the
.config and the full dmesg of the quadsocket machine?
Thanks.
--
Regards/Gruss,
Boris
next prev parent reply other threads:[~2010-02-01 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 23:16 nr_cpu_ids incorrect on AMD Quad-Core Opteron 8380 zhiyi
2010-01-30 17:18 ` Borislav Petkov
2010-01-31 22:59 ` zhiyi
2010-02-01 13:57 ` Borislav Petkov
2010-02-01 15:04 ` Borislav Petkov [this message]
2010-02-02 0:49 ` zhiyi
2010-02-02 7:07 ` Borislav Petkov
2010-02-02 21:33 ` zhiyi
2010-02-03 7:21 ` Borislav Petkov
2010-02-02 0:35 ` zhiyi
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=9ea470501002010704m15dfaedau813b7accfd1d22ff@mail.gmail.com \
--to=petkovbb@googlemail.com \
--cc=hzy@cs.otago.ac.nz \
--cc=jkmair@cs.otago.ac.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=zhuang@cs.otago.ac.nz \
/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