The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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: Tue, 2 Feb 2010 08:07:51 +0100	[thread overview]
Message-ID: <20100202070751.GA11623@liondog.tnic> (raw)
In-Reply-To: <4086DEE4-5D26-4EED-8353-2C4F54238CAE@cs.otago.ac.nz>

On Tue, Feb 02, 2010 at 01:49:06PM +1300, zhiyi wrote:
> The dmesg relevant to nr_cpu_ids of the quad socket is:
> 
> [    0.000000] NR_CPUS:64 nr_cpumask_bits:64 nr_cpu_ids:32 nr_node_ids:4
> 

No, this is not the relevant info. I was actually looking for the MADT ACPI
table and whether there are disabled entries like so:

[    0.000000] ACPI: LAPIC (acpi-id[0x03] lapic-id[0x02] enabled)
[    0.000000] ACPI: LAPIC (acpi-id[0x04] lapic-id[0x03] enabled)
[    0.000000] ACPI: LAPIC (acpi-id[0x05] lapic-id[0x84] disabled)
[    0.000000] ACPI: LAPIC (acpi-id[0x06] lapic-id[0x85] disabled)

because if there are, nr_cpu_ids will include those when you don't boot
with "possible_cpus=N".

Anyhow, you can read this for more info: http://www.pubbs.net/kernel/200912/64310/

-- 
Regards/Gruss,
    Boris.

  reply	other threads:[~2010-02-02  7:08 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
2010-02-02  0:49         ` zhiyi
2010-02-02  7:07           ` Borislav Petkov [this message]
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=20100202070751.GA11623@liondog.tnic \
    --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