Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S267290AbSLMCfN>; Thu, 12 Dec 2002 21:35:13 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S267349AbSLMCfN>; Thu, 12 Dec 2002 21:35:13 -0500
Received: from e31.co.us.ibm.com ([32.97.110.129]:58616 "EHLO
	e31.co.us.ibm.com") by vger.kernel.org with ESMTP
	id <S267290AbSLMCfL> convert rfc822-to-8bit; Thu, 12 Dec 2002 21:35:11 -0500
Content-Type: text/plain; charset=US-ASCII
From: James Cleverdon <jamesclv@us.ibm.com>
Reply-To: jamesclv@us.ibm.com
Organization: IBM xSeries Linux Solutions
To: Zwane Mwaikambo <zwane@holomorphy.com>
Subject: Re: [PATCH][2.5][RFC] Using xAPIC apic address space on !Summit
Date: Thu, 12 Dec 2002 18:41:32 -0800
User-Agent: KMail/1.4.3
Cc: Martin Bligh <mbligh@us.ibm.com>, John Stultz <johnstul@us.ibm.com>,
       Linux Kernel <linux-kernel@vger.kernel.org>
References: <Pine.LNX.4.50.0212112105490.14901-100000@montezuma.mastecende.com> <200212121809.43698.jamesclv@us.ibm.com> <Pine.LNX.4.50.0212122116260.6931-100000@montezuma.mastecende.com>
In-Reply-To: <Pine.LNX.4.50.0212122116260.6931-100000@montezuma.mastecende.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7BIT
Message-Id: <200212121841.32381.jamesclv@us.ibm.com>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 2772
Lines: 62

On Thursday 12 December 2002 06:21 pm, Zwane Mwaikambo wrote:
> On Thu, 12 Dec 2002, James Cleverdon wrote:
> > On Thursday 12 December 2002 05:44 pm, Zwane Mwaikambo wrote:
> > > Hi,
> > > 	I've got an 32x SMP system which has an xAPIC but utilises flat
> > > addressing. This patch is to rename what was formerly x86_summit to
> > > x86_xapic (just to avoid confusion) and then select mask depending on
> > > that.
> > >
> > > Untested/uncompiled patch
> >
> > Hi Zwane,
> >
> > How can you have a 32-way SMP system with flat addressing?  There are
> > only 8 bits in the destination address field.  Even if you work around
> > that by assigning a set of CPUs to each dest addr bit, there can only be
> > 15 physical APIC IDs in flat mode.  To get to 32 you must switch into
> > clustered mode.
> >
> > Please tell me more.  I'm intrigued how this can be done.
>
> Hi James,
> 	with the xAPIC we can use the 8bit address space everywhere in
> physical destination mode. For example the ICR now has an 8bit space for
> destination.
>
> "Specifies the target processor or processors. This field is only used
> when the destination shorthand field is set to 00B. If the destination
> mode is set to physical, then bits 56 through 59 contain the APIC ID of
> the target processor for Pentium and P6 family processors and bits 56
> through 63 contain the APIC ID of the target processor the for Pentium 4
> and Intel Xeon processors. If the destination mode is set to logical, the
> interpretation of the 8-bit destination field depends on the settings of
> the DFR and LDR registers of the local APICs in all the processors in the
> system (see Section 8.6.2.,  Determining IPI Destination )."
> 	- System Developer's Manual vol3 p291
>
> Regards,
> 	Zwane

Sure you can physically address them, if you assign IDs using Intel's official 
xAPIC numbering scheme (which must be clustered for more than 7 CPUs).  But, 
you still don't have enough destination address bits to go around.  In flat 
mode, the kernel assumes you have one bit per CPU and phys IDs will be < 0xF.

Bill tells me that you may be doing this for an emulator.  Why not emulate 
clusered APIC mode, like the real hardware uses?

I know the name x86_summit doesn't really fit.  The summit patch should work 
for any xAPIC box that uses the system bus for interrupt delivery and has 
multiple APIC clusters.  Is that what you're working towards?

-- 
James Cleverdon
IBM xSeries Linux Solutions
{jamesclv(Unix, preferred), cleverdj(Notes)} at us dot ibm dot com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/