From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [RFC GIT PULL] "Nuke 386-DX/SX support" changes for v3.8
Date: Wed, 12 Dec 2012 11:00:40 -0800 [thread overview]
Message-ID: <50C8D458.4050006@zytor.com> (raw)
In-Reply-To: <CA+55aFzJX-EKC4Z98+KEaca0V27p8PxqZXiPox=TuuhytUTziw@mail.gmail.com>
On 12/12/2012 10:04 AM, Linus Torvalds wrote:
> On Tue, Dec 11, 2012 at 3:10 AM, Ingo Molnar <mingo@kernel.org> wrote:
>>
>> This tree removes ancient-386-CPUs support and thus zaps quite a
>> bit of complexity:
>
> Btw, I think we should probably at least consider taking this one step
> further, and remove the dear old FPU emulation support too. Remove
> CONFIG_MATH_EMULATION and all of arch/x86/math-emu, along with a lot
> of small special cases.
>
> Or do people still use the 486SX?
>
> Now, the math emulation hasn't been all that fundamentally problematic
> (compared to lack of xadd etc), but it does result in some
> complexities in exception handling and ptrace (grep for HAVE_HWFP or
> "hard_math" or a number of other magic things). None of which have
> likely been tested at all in the last ten years, so who knows if it
> actually *works* or not.
>
> Maybe somebody could try booting with "no387". Does it actually work?
>
It builds and boots, at least. I'm currently installing Red Hat 4.1 in
a VM so I can test to see if it does anything more than that. It
doesn't get in the way the same case the old 386 bits does, so I'm more
reluctant to remove it, but it does touch a lot of paths.
There were a *bunch* of embedded 486 clones made, some still in
production as far as I know, and I wouldn't be surprised if some of them
lacked FPU. I guess we'll see.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-12-12 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 11:10 [RFC GIT PULL] "Nuke 386-DX/SX support" changes for v3.8 Ingo Molnar
2012-12-12 18:04 ` Linus Torvalds
2012-12-12 19:00 ` H. Peter Anvin [this message]
2012-12-12 22:24 ` H. Peter Anvin
2012-12-13 16:05 ` Linus Torvalds
2012-12-13 11:15 ` Bernd Petrovitsch
2012-12-13 12:13 ` Thorsten Glaser
2012-12-13 16:23 ` Florian Fainelli
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=50C8D458.4050006@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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