From: Matt Domsch <Matt_Domsch@dell.com>
To: Andi Kleen <ak@muc.de>
Cc: YhLu <YhLu@tyan.com>, linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: 256 apic id for amd64
Date: Thu, 30 Dec 2004 16:56:02 -0600 [thread overview]
Message-ID: <20041230225602.GA27670@lists.us.dell.com> (raw)
In-Reply-To: <m1d5wrlj5p.fsf@muc.de>
On Thu, Dec 30, 2004 at 07:45:22PM +0100, Andi Kleen wrote:
> i386 also has a different (but Intel specific fix) - uses either
> 0xf or 0xff based on the APIC version. Just dropping it seems
> better to me though. I suppose Matt (cc'ed) who apparently
> wrote this code originally used it to work around some BIOS
> bug, and at least we can hope for now that there are no
> EM64T boxes with that particular BIOS bug.
The MPC spec (I don't have a copy handy anymore) said it's the OS's
job to program the APIC ID into the processor based on what BIOS put
in the MP Table for it. At the time I wrote the patch, the kernel
didn't do this, so now it does, else all CPUs could wind up with the
same APIC ID, which messed up interrupt routing IIRC.
What's differrent about this x86_64 system in this regard please?
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-12-30 22:56 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-29 4:43 256 apic id for amd64 YhLu
2004-12-30 18:45 ` Andi Kleen
2004-12-30 22:56 ` Matt Domsch [this message]
2004-12-30 23:26 ` Andi Kleen
2004-12-30 23:16 YhLu
2004-12-30 23:19 YhLu
2005-01-07 1:06 YhLu
2005-01-07 12:44 ` 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 18:19 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 18:27 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 19:43 YhLu
2005-01-07 19:40 ` Andi Kleen
2005-01-07 21:14 YhLu
2005-01-07 21:12 ` Andi Kleen
2005-01-07 21:44 YhLu
2005-01-07 22:18 ` Andi Kleen
2005-01-08 0:04 YhLu
2005-01-08 0:12 ` James Cleverdon
2005-01-08 0:28 YhLu
2005-01-08 0:26 ` James Cleverdon
2005-01-08 0:34 ` Andi Kleen
2005-01-08 0:50 YhLu
2005-01-08 0:42 ` Andi Kleen
2005-01-08 1:50 YhLu
2005-01-08 2:37 Mikael Pettersson
2005-01-08 15:46 ` Andi Kleen
2005-01-08 2:53 YhLu
2005-01-09 23:56 ` James Cleverdon
2005-01-10 18:44 Andi Kleen
2005-01-11 4:04 ` Siddha, Suresh B
2005-01-11 4:39 ` Andi Kleen
2005-01-11 17:50 ` Andi Kleen
2005-01-10 18:48 YhLu
2005-01-10 18:45 ` 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 20:09 YhLu
2005-01-10 20:18 ` Andi Kleen
2005-01-10 20:37 YhLu
2005-01-10 20:46 YhLu
2005-01-11 5:36 ` Andi Kleen
2005-01-10 20:48 YhLu
2005-01-11 19:04 YhLu
2005-01-11 19:11 YhLu
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=20041230225602.GA27670@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=YhLu@tyan.com \
--cc=ak@muc.de \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).