From: Christoph Lameter <cl@linux-foundation.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
Giangiacomo Mariotti <gg.mariotti@gmail.com>,
Bill Davidsen <davidsen@tmr.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
x86 maintainers <x86@kernel.org>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Possible bug in 2.6.34 slub
Date: Thu, 3 Jun 2010 08:34:20 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1006030833070.24954@router.home> (raw)
In-Reply-To: <AANLkTinxOJShwd7xUornVI89BmJnbX9-a7LVWaciNdr5@mail.gmail.com>
On Thu, 3 Jun 2010, Pekka Enberg wrote:
> On Tue, Jun 1, 2010 at 10:48 PM, Christoph Lameter
> <cl@linux-foundation.org> wrote:
> > On Tue, 1 Jun 2010, Randy Dunlap wrote:
> >
> >> > >>> My cpu is an I7 920, so it has 4 cores and there's hyperthreading
> >> > >>> enabled, so there are 8 logical cpus. Is this a bug?
> >
> > Yes its a bug in the arch code or BIOS. The system configuration tells us
> > that there are more possible cpus and therefore the system prepares for
> > the additional cpus to be activated at some later time.
>
> I guess we should CC x86 maintainers then!
Its also a know BIOS problem with Dell f.e. They often indicate more
potential cpus even if this particular hw configuration cannot do cpu
hotplug.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-06-03 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimEFy6VM3InWlqhVooQjKGSD3yBxlgeRbQC2r1L@mail.gmail.com>
[not found] ` <20100531165528.35a323fb.rdunlap@xenotime.net>
[not found] ` <4C047CF9.9000804@tmr.com>
[not found] ` <AANLkTilLq-hn59CBcLnOsnT37ZizQR6MrZX6btKPhfpb@mail.gmail.com>
2010-06-01 19:39 ` Randy Dunlap
2010-06-01 19:48 ` Christoph Lameter
2010-06-01 21:11 ` Giangiacomo Mariotti
2010-06-01 21:27 ` Christoph Lameter
2010-06-03 6:51 ` Pekka Enberg
2010-06-03 13:34 ` Christoph Lameter [this message]
2010-06-04 18:39 ` Giangiacomo Mariotti
2010-06-07 22:35 ` Christoph Lameter
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=alpine.DEB.2.00.1006030833070.24954@router.home \
--to=cl@linux-foundation.org \
--cc=davidsen@tmr.com \
--cc=gg.mariotti@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rdunlap@xenotime.net \
--cc=x86@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