summaryrefslogtreecommitdiff
path: root/mm/truncate.c
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2019-08-05 12:34:51 +0300
committerMarc Zyngier <maz@kernel.org>2019-08-09 10:07:24 +0300
commitc69509c70aa45a8c4954c88c629a64acf4ee4a36 (patch)
tree3d8420ab6e0a487a894040a13b3ba44c924f1ee9 /mm/truncate.c
parent03fdfb2690099c19160a3f2c5b77db60b3afeded (diff)
downloadlinux-c69509c70aa45a8c4954c88c629a64acf4ee4a36.tar.xz
KVM: arm: Don't write junk to CP15 registers on reset
At the moment, the way we reset CP15 registers is mildly insane: We write junk to them, call the reset functions, and then check that we have something else in them. The "fun" thing is that this can happen while the guest is running (PSCI, for example). If anything in KVM has to evaluate the state of a CP15 register while junk is in there, bad thing may happen. Let's stop doing that. Instead, we track that we have called a reset function for that register, and assume that the reset function has done something. In the end, the very need of this reset check is pretty dubious, as it doesn't check everything (a lot of the CP15 reg leave outside of the cp15_regs[] array). It may well be axed in the near future. Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'mm/truncate.c')
0 files changed, 0 insertions, 0 deletions