kconfig: Rename CONFIG_FLOAT to CONFIG_FPU
This commit renames the Kconfig `FLOAT` symbol to `FPU`, since this symbol only indicates that the hardware Floating Point Unit (FPU) is used and does not imply and/or indicate the general availability of toolchain-level floating point support (i.e. this symbol is not selected when building for an FPU-less platform that supports floating point operations through the toolchain-provided software floating point library). Moreover, given that the symbol that indicates the availability of FPU is named `CPU_HAS_FPU`, it only makes sense to use "FPU" in the name of the symbol that enables the FPU. Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
This commit is contained in:
parent
3230a85590
commit
0e6ede8929
56 changed files with 114 additions and 115 deletions
|
@ -80,7 +80,7 @@ depends on CPU_HAS_FPU
|
|||
|
||||
config SSE
|
||||
bool "SSE registers"
|
||||
depends on FLOAT
|
||||
depends on FPU
|
||||
help
|
||||
This option enables the use of SSE registers by threads.
|
||||
|
||||
|
@ -100,7 +100,7 @@ config SSE_FP_MATH
|
|||
|
||||
config EAGER_FP_SHARING
|
||||
bool
|
||||
depends on FLOAT
|
||||
depends on FPU
|
||||
depends on USERSPACE
|
||||
default y if !X86_NO_LAZY_FP
|
||||
help
|
||||
|
@ -110,12 +110,12 @@ config EAGER_FP_SHARING
|
|||
Mitigates CVE-2018-3665, but incurs a performance hit.
|
||||
|
||||
For vulnerable systems that process sensitive information in the
|
||||
FPU register set, should be used any time CONFIG_FLOAT is
|
||||
FPU register set, should be used any time CONFIG_FPU is
|
||||
enabled, regardless if the FPU is used by one thread or multiple.
|
||||
|
||||
config LAZY_FP_SHARING
|
||||
bool
|
||||
depends on FLOAT
|
||||
depends on FPU
|
||||
depends on !EAGER_FP_SHARING
|
||||
depends on FP_SHARING
|
||||
default y if X86_NO_LAZY_FP || !USERSPACE
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue