From: Ingo Molnar <mingo@kernel.org>
To: Denys Vlasenko <dvlasenk@redhat.com>
Cc: Jiang Liu <jiang.liu@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Len Brown <len.brown@intel.com>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86_64: MAX_LOCAL_APIC way too big?
Date: Sat, 26 Sep 2015 08:08:12 +0200 [thread overview]
Message-ID: <20150926060812.GA27630@gmail.com> (raw)
In-Reply-To: <56057344.2070206@redhat.com>
* Denys Vlasenko <dvlasenk@redhat.com> 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
prev parent reply other threads:[~2015-09-26 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 16:16 x86_64: MAX_LOCAL_APIC way too big? Denys Vlasenko
2015-09-25 16:56 ` Jiang Liu
2015-09-25 19:44 ` Denys Vlasenko
2015-09-26 6:08 ` Ingo Molnar [this message]
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=20150926060812.GA27630@gmail.com \
--to=mingo@kernel.org \
--cc=dvlasenk@redhat.com \
--cc=jiang.liu@linux.intel.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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