mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RFD: Does CONFIG_X86_LOCAL_APIC still make sense?
Date: Thu, 10 Oct 2013 16:04:25 -0700	[thread overview]
Message-ID: <52573279.9020404@zytor.com> (raw)

I'm trying to wrap my head around if there are use cases where disabling
either CONFIG_X86_UP_APIC or CONFIG_X86_LOCAL_APIC would ever make sense
anymore.

I am guessing there are probably some small number of embedded systems
which still don't have LAPICs, but is it a significant number and does
anyone care for new kernels?  We are not talking about discontinuing
support for non-APIC configurations, just the configuration option.

	-hpa

             reply	other threads:[~2013-10-10 23:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 23:04 H. Peter Anvin [this message]
2013-10-11  6:20 ` Ingo Molnar

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=52573279.9020404@zytor.com \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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
Powered by JetHome