From: Randy Dunlap <rdunlap@xenotime.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: akpm <akpm@osdl.org>, Jesper Juhl <jesper.juhl@gmail.com>,
Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] Math-emu kills the kernel on Athlon64 X2
Date: Tue, 3 Oct 2006 09:49:26 -0700 [thread overview]
Message-ID: <20061003094926.0e99d13f.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0610030933250.3952@g5.osdl.org>
On Tue, 3 Oct 2006 09:37:45 -0700 (PDT) Linus Torvalds wrote:
>
>
> On Tue, 3 Oct 2006, Randy Dunlap wrote:
> >
> > Yes, that works.
>
> Ok. I'll commit that simple thing, and add a comment on why we're
> apparently doing the same thing twice (you do need _both_ of those things:
> the "disable_x86_fxsr" will make sure all other CPU's also get cleared,
> while the "clear_bit()" will clear it immediately on the boot CPU)
>
> I'll leave the no387/nofxsr linking alone for now. The main reason to use
> no387 would seem to be just testing that emulation works at all, and I
> guess we can just tell people to use the "no387 nofxsr" combination.
>
> So Randy, with this you can boot all the way into user space, and some FP
> apps still work too?
My few trivial float and double apps work.
Is there any particular test/workload that you want me to run?
> (Of course, user-space may be buggy and use SSE etc without testing for
> whether the CPU actually supports it - if the install process has
> installed some special SSE-version of a library depending on what the CPU
> claimed at that point, or if somebody uses "cpuid" directly rather than
> asking the kernel. So there's no way we're going to _guarantee_ that this
> works in user space, but at least a well-behaved user-space that works on
> a i486 should hopefully be ok).
---
~Randy
next prev parent reply other threads:[~2006-10-03 16:48 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 22:18 Jesper Juhl
2006-09-18 22:52 ` Linus Torvalds
2006-09-18 23:14 ` Jesper Juhl
2006-09-18 23:49 ` Linus Torvalds
2006-09-19 0:47 ` Jesper Juhl
2006-09-19 2:18 ` Linus Torvalds
2006-09-18 23:49 ` Sergio Monteiro Basto
2006-09-19 0:02 ` Jesper Juhl
2006-09-19 12:28 ` Krzysztof Halasa
2006-09-20 0:48 ` Sergio Monteiro Basto
2006-09-20 22:31 ` Krzysztof Halasa
2006-09-19 8:01 ` Andi Kleen
2006-09-19 8:31 ` Jesper Juhl
2006-09-19 21:14 ` Jesper Juhl
2006-09-19 22:01 ` Linus Torvalds
2006-09-19 22:16 ` Jesper Juhl
2006-09-19 22:44 ` Jesper Juhl
2006-10-03 2:16 ` [PATCH/RFC] " Randy Dunlap
2006-10-03 2:34 ` Linus Torvalds
2006-10-03 3:24 ` Randy Dunlap
2006-10-03 10:05 ` Andi Kleen
2006-10-03 14:54 ` Linus Torvalds
2006-10-03 10:11 ` [PATCH/RFC] Math-emu kills the kernel on Athlon64 X2 II -- it's terminally broken Andi Kleen
2006-10-03 11:53 ` Alan Cox
2006-10-03 14:48 ` Linus Torvalds
2006-10-03 4:38 ` [PATCH/RFC] Math-emu kills the kernel on Athlon64 X2 Randy Dunlap
2006-10-03 11:30 ` Alan Cox
2006-10-03 15:10 ` Linus Torvalds
2006-10-03 16:23 ` Randy Dunlap
2006-10-03 16:37 ` Linus Torvalds
2006-10-03 16:49 ` Randy Dunlap [this message]
2006-10-03 16:51 ` Linus Torvalds
2006-10-04 19:24 ` Jesper Juhl
2006-10-04 19:43 ` Linus Torvalds
2006-10-04 20:02 ` Jesper Juhl
2006-10-04 22:00 ` Alan Cox
2006-10-04 21:44 ` Andi Kleen
2006-09-20 8:16 ` Andi Kleen
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=20061003094926.0e99d13f.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®