From: Dave Jones <davej@codemonkey.org.uk>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86: Cleanup Kconfig
Date: Wed, 3 Jun 2015 09:59:16 -0400 [thread overview]
Message-ID: <20150603135915.GA4446@codemonkey.org.uk> (raw)
In-Reply-To: <20150603074132.GA1092@gmail.com>
On Wed, Jun 03, 2015 at 09:41:32AM +0200, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@kernel.org> wrote:
>
> > select GENERIC_CLOCKEVENTS_BROADCAST if X86_64 || (X86_32 && X86_LOCAL_APIC)
>
> Btw., could we (in a separate patch) turn this into:
>
> > select GENERIC_CLOCKEVENTS_BROADCAST
>
> x86 systems without an APIC are rare and rarely tested, we are better off
> simplifying our clockevents layout.
There's a ton of code in arch/x86 for cpus that don't have apic.
Anything Cyrix pre-VIA buy out, Anything AMD pre Athlon,
did Intel have apic on 486 ? Transmeta ?
I'm all for abandoning support for 2 decade old junk, but given how
long it took to drop 386, I wouldn't be surprised if there are still
a lot of 586 era people still out there playing doom and wearing
clothes that are about to come back into fashion.
Dave
next prev parent reply other threads:[~2015-06-03 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 9:14 [RFC][PATCH] x86: Cleanup Kconfig Peter Zijlstra
2015-06-02 11:35 ` Ingo Molnar
2015-06-02 15:30 ` Peter Zijlstra
2015-06-03 7:26 ` Ingo Molnar
2015-06-03 7:41 ` Ingo Molnar
2015-06-03 13:59 ` Dave Jones [this message]
2015-06-03 16:19 ` Ingo Molnar
2015-06-03 17:11 ` Dave Jones
2015-06-03 9:30 ` [tip:x86/core] x86/kconfig: Reorganize arch feature Kconfig select's tip-bot for 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=20150603135915.GA4446@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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