diff options
author | Arnd Bergmann <arnd.bergmann@de.ibm.com> | 2006-06-20 02:30:33 +0200 |
---|---|---|
committer | Paul Mackerras <paulus@samba.org> | 2006-06-21 15:01:33 +1000 |
commit | ddf5f75a16b3e7460ffee881795aa168dffcd0cf (patch) | |
tree | 28149044321f1f7e39a957b3eed3cc6537229536 /include/linux | |
parent | 72abd54035a3d71fd8f02596e659257e8bba16ca (diff) | |
download | kernel_samsung_smdk4412-ddf5f75a16b3e7460ffee881795aa168dffcd0cf.zip kernel_samsung_smdk4412-ddf5f75a16b3e7460ffee881795aa168dffcd0cf.tar.gz kernel_samsung_smdk4412-ddf5f75a16b3e7460ffee881795aa168dffcd0cf.tar.bz2 |
[POWERPC] disable floating point exceptions for init
Floating point exceptions should not be enabled by default,
as this setting impacts the performance on some CPUs, in
particular the Cell BE. Since the bits are inherited from
parent processes, the place to change the default is the
thread struct used for init.
glibc sets this up correctly per thread in its fesetenv
function, so user space should not be impacted by this
setting. None of the other common libc implementations
(uClibc, dietlibc, newlib, klibc) has support for fp
exceptions, so they are unlikely to be hit by this either.
There is a small risk that somebody wrote their own
application that manually sets the fpscr bits instead
of calling fesetenv, without changing the MSR bits as well.
Those programs will break with this change.
It probably makes sense to change glibc in the future
to be more clever about FE bits, so that when running
on a CPU where this is expensive, it disables exceptions
ASAP, while it keeps them enabled on CPUs where running
with exceptions on is cheaper than changing the state
often.
Signed-off-by: Arnd Bergmann <arnd.bergmann@de.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions