From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751145AbbIZGIR (ORCPT ); Sat, 26 Sep 2015 02:08:17 -0400 Received: from mail-wi0-f175.google.com ([209.85.212.175]:35209 "EHLO mail-wi0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750767AbbIZGIQ (ORCPT ); Sat, 26 Sep 2015 02:08:16 -0400 Date: Sat, 26 Sep 2015 08:08:12 +0200 From: Ingo Molnar To: Denys Vlasenko Cc: Jiang Liu , Thomas Gleixner , Len Brown , X86 ML , LKML Subject: Re: x86_64: MAX_LOCAL_APIC way too big? Message-ID: <20150926060812.GA27630@gmail.com> References: <56057344.2070206@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <56057344.2070206@redhat.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Denys Vlasenko wrote: > For 64-bit kernels, MAX_LOCAL_APIC is 32k: > > #ifdef CONFIG_X86_32 > ... > #else > # define MAX_IO_APICS 128 > # define MAX_LOCAL_APIC 32768 > #endif > > (It seems to be a bit of a misnomer, it's not a maximum > number of APICs we support, it's the highest APIC _id_ > we support.) Gah, that's a pretty serious misnomer - so it should be fixed regardless of the outcome of the sizing discussion. Thanks, Ingo