diff options
author | Ralf Baechle <ralf@linux-mips.org> | 2014-12-17 10:39:30 (GMT) |
---|---|---|
committer | Ralf Baechle <ralf@linux-mips.org> | 2015-01-13 14:53:08 (GMT) |
commit | b0c34f6155e2d8bbe096a85a770d63ee6be6c726 (patch) | |
tree | 85e04f8504b0dd06798c09bd2e56e27edbe852a2 /arch/mips/kvm | |
parent | eaa27f34e91a14cdceed26ed6c6793ec1d186115 (diff) | |
download | linux-b0c34f6155e2d8bbe096a85a770d63ee6be6c726.tar.xz |
MIPS: Do not fiddle with FRE unless FRE is actually available.
Commit 4227a2d4efc9c84f35826dc4d1e6dc183f6c1c05 (MIPS: Support for hybrid
FPRs) changes the kernel to execute read_c0_config5() even on processors
that don't have a Config5 register. According to the arch spec the
behaviour of trying to read or write this register is UNDEFINED where this
register doesn't exist, that is merely looking at this register is
already cruel because that might kill a kitten.
In case of Qemu older than v2.2 Qemu has elected to implement this
UNDEFINED behaviour by taking a RI exception - which then fries the
kernel:
[...]
Freeing YAMON memory: 956k freed
Freeing unused kernel memory: 240K (80674000 - 806b0000)
Reserved instruction in kernel code[#1]:
CPU: 0 PID: 1 Comm: init Not tainted 3.18.0-rc6-00058-g4227a2d #26
task: 86047588 ti: 86048000 task.ti: 86048000
$ 0 : 00000000 77a638cc 00000000 00000000
[...]
For qemu v2.2.0 commit f31b035a9f10dc9b57f01c426110af845d453ce2
(target-mips: correctly handle access to unimplemented CP0 register)
changed the behaviour to returning zero on read and ignoring writes
which more matches how typical hardware implementations actually behave.
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
Diffstat (limited to 'arch/mips/kvm')
0 files changed, 0 insertions, 0 deletions