Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 12 Dec 2002 22:15:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 12 Dec 2002 22:15:42 -0500 Received: from modemcable092.130-200-24.mtl.mc.videotron.ca ([24.200.130.92]:59093 "EHLO montezuma.mastecende.com") by vger.kernel.org with ESMTP id ; Thu, 12 Dec 2002 22:15:37 -0500 Date: Thu, 12 Dec 2002 22:26:05 -0500 (EST) From: Zwane Mwaikambo X-X-Sender: zwane@montezuma.mastecende.com To: "Nakajima, Jun" cc: jamesclv@us.ibm.com, Martin Bligh , John Stultz , Linux Kernel Subject: RE: [PATCH][2.5][RFC] Using xAPIC apic address space on !Summit In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 720 Lines: 20 On Thu, 12 Dec 2002, Nakajima, Jun wrote: > BTW, we are working on a xAPIC patch that supports more than 8 CPUs in a > generic fashion (don't use hardcode OEM checking). We already tested it on > two OEM systems with 16 CPUs. > - It uses clustered mode. We don't want to use physical mode because it does > not support lowest priority delivery mode. Wouldn't that only be for all including self? Or is the documentation incorrect? Thanks, Zwane -- function.linuxpower.ca - 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/