diff options
| author | Hendrik Brueckner <brueckner@linux.vnet.ibm.com> | 2015-09-29 10:04:41 +0200 |
|---|---|---|
| committer | Martin Schwidefsky <schwidefsky@de.ibm.com> | 2015-10-14 14:32:08 +0200 |
| commit | b5510d9b68c33964abd938148f407ad3789e369f (patch) | |
| tree | 7cf0eb3e5e74e861030f850c8c0894095ac70bc9 /arch/s390/kernel/entry.h | |
| parent | 395e6aa1d0ffbc493a04469aa8f6751ed2aad8c5 (diff) | |
| download | talos-obmc-linux-b5510d9b68c33964abd938148f407ad3789e369f.tar.gz talos-obmc-linux-b5510d9b68c33964abd938148f407ad3789e369f.zip | |
s390/fpu: always enable the vector facility if it is available
If the kernel detects that the s390 hardware supports the vector
facility, it is enabled by default at an early stage. To force
it off, use the novx kernel parameter. Note that there is a small
time window, where the vector facility is enabled before it is
forced to be off.
With enabling the vector facility by default, the FPU save and
restore functions can be improved. They do not longer require
to manage expensive control register updates to enable or disable
the vector enablement control for particular processes.
Signed-off-by: Hendrik Brueckner <brueckner@linux.vnet.ibm.com>
Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Diffstat (limited to 'arch/s390/kernel/entry.h')
| -rw-r--r-- | arch/s390/kernel/entry.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/s390/kernel/entry.h b/arch/s390/kernel/entry.h index 834df047d35f..3eecd0f7adb2 100644 --- a/arch/s390/kernel/entry.h +++ b/arch/s390/kernel/entry.h @@ -21,8 +21,6 @@ void psw_idle(struct s390_idle_data *, unsigned long); asmlinkage long do_syscall_trace_enter(struct pt_regs *regs); asmlinkage void do_syscall_trace_exit(struct pt_regs *regs); -int alloc_vector_registers(struct task_struct *tsk); - void do_protection_exception(struct pt_regs *regs); void do_dat_exception(struct pt_regs *regs); |
