linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Andi Kleen <ak@muc.de>
Cc: Yinghai Lu <yhlu@tyan.com>,
	"'Mikael Pettersson'" <mikpe@csd.uu.se>,
	jamesclv@us.ibm.com, Matt_Domsch@dell.com, discuss@x86-64.org,
	linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com
Subject: Re: 256 apic id for amd64
Date: Mon, 10 Jan 2005 20:04:25 -0800	[thread overview]
Message-ID: <20050110200425.B30630@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050110184437.GA74665@muc.de>; from ak@muc.de on Mon, Jan 10, 2005 at 07:44:37PM +0100

YH, I suggest you root cause the exact issue and if it turns out to
be a platform issue, then we can have a kernel workaround for that specific
platform. As Andi mentioned, we don't have any kernel limitations with
BSP apicid != 0.

On Mon, Jan 10, 2005 at 07:44:37PM +0100, Andi Kleen wrote:
> On Mon, Jan 10, 2005 at 10:32:42AM -0800, Yinghai Lu wrote:
> > Case 1: lift core0/node0 to use 16, and core1/node0 to use 17.....
> > Case 2: core0/node0-->0, core1/node0-->1, core0/node1-->18,
> > core1/node1-->19...
> > Case 3: core0/node0-->0, core1/node0-->17, core0/node1-->18,
> > core1/node1-->19...
> > 
> > Case 1 will make jiffies not happy and it will hang on calibrate_dalay. (
> > jiffies is not changing).
> 
> That's because it needs physical APIC mode to handle CPU IDs >7, and that is
>  not implemented in the flat case. I added it now, but you likely don't need 
> it anyways.

Andi, we don't need physical APIC mode just to handle CPU APIC ID's > 7
when the total number of cpu's in the system is < 8. Right?

thanks,
suresh

  reply	other threads:[~2005-01-11  4:08 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-10 18:44 256 apic id for amd64 Andi Kleen
2005-01-11  4:04 ` Siddha, Suresh B [this message]
2005-01-11  4:39   ` Andi Kleen
2005-01-11 17:50   ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-01-11 19:11 YhLu
2005-01-11 19:04 YhLu
2005-01-10 20:48 YhLu
2005-01-10 20:46 YhLu
2005-01-11  5:36 ` Andi Kleen
2005-01-10 20:37 YhLu
2005-01-10 20:09 YhLu
2005-01-10 20:18 ` Andi Kleen
2005-01-10 19:41 YhLu
2005-01-10 19:43 ` Andi Kleen
2005-01-11  0:42 ` James Cleverdon
2005-01-11  3:28   ` Siddha, Suresh B
2005-01-11  4:42     ` Andi Kleen
2005-01-10 18:48 YhLu
2005-01-10 18:45 ` Andi Kleen
2005-01-08  2:53 YhLu
2005-01-09 23:56 ` James Cleverdon
2005-01-08  2:37 Mikael Pettersson
2005-01-08 15:46 ` Andi Kleen
2005-01-08  1:50 YhLu
2005-01-08  0:50 YhLu
2005-01-08  0:42 ` Andi Kleen
2005-01-08  0:28 YhLu
2005-01-08  0:26 ` James Cleverdon
2005-01-08  0:34   ` Andi Kleen
2005-01-08  0:04 YhLu
2005-01-08  0:12 ` James Cleverdon
2005-01-07 21:44 YhLu
2005-01-07 22:18 ` Andi Kleen
2005-01-07 21:14 YhLu
2005-01-07 21:12 ` Andi Kleen
2005-01-07 19:43 YhLu
2005-01-07 19:40 ` Andi Kleen
2005-01-07 18:27 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 18:19 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07  2:53 YhLu
2005-01-07 12:24 ` Andi Kleen
2005-01-08  1:30   ` James Cleverdon
2005-01-07  1:06 YhLu
2005-01-07 12:44 ` Andi Kleen
2004-12-30 23:19 YhLu
2004-12-30 23:16 YhLu
2004-12-29  4:43 YhLu
2004-12-30 18:45 ` Andi Kleen
2004-12-30 22:56   ` Matt Domsch
2004-12-30 23:26     ` 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=20050110200425.B30630@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=Matt_Domsch@dell.com \
    --cc=ak@muc.de \
    --cc=discuss@x86-64.org \
    --cc=jamesclv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=yhlu@tyan.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;
as well as URLs for NNTP newsgroup(s).