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?
(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).
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
