From: Andi Kleen <ak@suse.de>
To: yhlu <yhlu.kernel@gmail.com>
Cc: Andi Kleen <ak@suse.de>,
discuss@x86-64.org, linux-kernel@vger.kernel.org,
linuxbios@openbios.org
Subject: Re: x86_64: apic id lift patch
Date: Tue, 22 Nov 2005 10:44:18 +0100 [thread overview]
Message-ID: <20051122094417.GI20775@brahms.suse.de> (raw)
In-Reply-To: <86802c440511211431p57628e01o5c8030c4e09deaba@mail.gmail.com>
On Mon, Nov 21, 2005 at 02:31:44PM -0800, yhlu wrote:
> >
> > max_cores should be 2 here.
> No, For E0 single core, x86_max_cores will be 1, the initial apicid
> can not be shifted to node id....
> >
> >
> > Is there a good reason in the BIOS to not make it contiguous?
> >
> amd8111, if i lift the bsp apic id, the jiffies will not be moving....,
It works for other BIOS, so something must be wrong in your setup.
Better root cause that.
-Andi
next prev parent reply other threads:[~2005-11-22 9:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 21:49 x86_64: apic id lift patch yhlu
2005-11-21 22:06 ` Andi Kleen
2005-11-21 22:17 ` yhlu
2005-11-21 22:24 ` Andi Kleen
2005-11-21 22:31 ` yhlu
2005-11-22 9:44 ` Andi Kleen [this message]
2005-11-23 16:58 ` [LinuxBIOS] " Ronald G Minnich
2005-11-23 17:35 ` Andi Kleen
[not found] ` <2ea3fae10511230943y5f697eb8sdbf891497fa8b88f@mail.gmail.com>
2005-11-23 17:50 ` Andi Kleen
2005-11-23 18:01 ` yhlu
2005-11-23 20:29 ` [discuss] " Andi Kleen
2005-11-23 20:29 ` Ronald G Minnich
2005-11-23 18:28 ` Stefan Reinauer
2005-11-23 20:26 ` Ronald G Minnich
[not found] ` <2ea3fae10511230919l4d9829d8j3ce5d820b74074d1@mail.gmail.com>
2005-11-23 17:36 ` Andi Kleen
2005-11-23 17:40 ` yhlu
2005-11-23 18:18 ` Stefan Reinauer
2005-11-23 18:22 ` yhlu
2005-11-23 18:35 ` yhlu
2005-11-23 20:28 ` [discuss] " Andi Kleen
2005-11-23 18:17 ` Stefan Reinauer
2005-11-23 20:23 ` Ronald G Minnich
2005-11-23 20:34 ` [discuss] " Andi Kleen
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=20051122094417.GI20775@brahms.suse.de \
--to=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxbios@openbios.org \
--cc=yhlu.kernel@gmail.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