All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Wilck <martin.wilck@fujitsu-siemens.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC version and 8-bit APIC IDs
Date: Fri, 12 Aug 2005 15:21:00 +0200	[thread overview]
Message-ID: <42FCA23C.7040601@fujitsu-siemens.com> (raw)
In-Reply-To: <p73pssj2xdz.fsf@verdi.suse.de>

Andi Kleen wrote:

> Yes, it's broken. In fact I removed it in my physflat32 patch
> which is needed for 16 core AMD systems. I don't think there
> is a generic way to fix it because the XAPIC check breaks
> on AMD systems 

on the Intel Xeon MP systems, too,

> and there is no good way to decide early 
> on subarchitectures before doing this check. Also it's only
> a sanity check for broken BIOS, and in this case it causes more problems
> than it solves.

agreed.

> ftp://ftp.firstfloor.org/pub/ak/x86_64/x86_64-2.6.13rc3-1/patches/physflat32

That is a beautiful patch, thank you.

Only one small point: I wonder whether it is correct to use the number 
of CPUs as criterion for this architecture. AFAICS, the Specs allow
having only 4 CPUS, but giving them APIC IDs e.g. 16,17,18,19. In this 
case, physflat32 should be used as well (in particular, the APIC ID 
broadcast and mask must be set to 0xff).

> Will hopefully be fixed in 2.6.14.

Great,

Martin

-- 
Martin Wilck                Phone: +49 5251 8 15113
Fujitsu Siemens Computers   Fax:   +49 5251 8 20409
Heinz-Nixdorf-Ring 1        mailto:Martin.Wilck@Fujitsu-Siemens.com
D-33106 Paderborn           http://www.fujitsu-siemens.com/primergy

  reply	other threads:[~2005-08-12 13:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42FC8461.2040102@fujitsu-siemens.com.suse.lists.linux.kernel>
2005-08-12 11:43 ` APIC version and 8-bit APIC IDs Andi Kleen
2005-08-12 13:21   ` Martin Wilck [this message]
2005-08-12 13:32     ` Andi Kleen
2005-08-12 13:51       ` Martin Wilck
2005-08-12 14:55         ` Martin Wilck
2005-08-12 14:57           ` Andi Kleen
2005-08-12 16:37             ` yhlu
2005-08-12 16:42               ` Andi Kleen
2005-08-12 17:44                 ` yhlu
2005-08-22  9:50                   ` Martin Wilck
2005-08-23 11:10                     ` Maciej W. Rozycki
2005-08-26 14:01                       ` Martin Wilck
2005-08-26 14:50                         ` Maciej W. Rozycki
2005-08-29  7:25                           ` Martin Wilck
2005-08-12 18:19             ` Siddha, Suresh B
2005-08-12 18:22               ` Andi Kleen
2005-08-12 18:40                 ` Siddha, Suresh B
2005-08-12 18:50                   ` Andi Kleen
2005-08-31 13:13   ` Martin Wilck
2005-08-31 13:25     ` Maciej W. Rozycki
2005-08-31 14:27       ` Martin Wilck
     [not found]       ` <4315B2D9.6080700@fujitsu-siemens.com>
     [not found]         ` <Pine.LNX.4.61L.0508311450020.10940@blysk.ds.pg.gda.pl>
2005-08-31 14:50           ` Martin Wilck
2005-08-31 14:40     ` Andi Kleen
2005-08-12 11:13 Martin Wilck

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=42FCA23C.7040601@fujitsu-siemens.com \
    --to=martin.wilck@fujitsu-siemens.com \
    --cc=ak@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.