diff options
author | Suraj Jitindar Singh <sjitindarsingh@gmail.com> | 2019-04-30 10:41:23 +1000 |
---|---|---|
committer | Paul Mackerras <paulus@ozlabs.org> | 2019-04-30 19:32:19 +1000 |
commit | 44b198aee1f2649534bdf08bfd7517c56da2ed7e (patch) | |
tree | f6b694a6df88e7c1eb0029c32da4e525becf1a73 /net | |
parent | 70ea13f6e609e8762d9f57287ebf873a18c91a44 (diff) | |
download | linux-44b198aee1f2649534bdf08bfd7517c56da2ed7e.tar.gz linux-44b198aee1f2649534bdf08bfd7517c56da2ed7e.tar.bz2 linux-44b198aee1f2649534bdf08bfd7517c56da2ed7e.zip |
KVM: PPC: Book3S HV: Save/restore vrsave register in kvmhv_p9_guest_entry()
On POWER9 and later processors where the host can schedule vcpus on a
per thread basis, there is a streamlined entry path used when the guest
is radix. This entry path saves/restores the fp and vr state in
kvmhv_p9_guest_entry() by calling store_[fp/vr]_state() and
load_[fp/vr]_state(). This is the same as the old entry path however the
old entry path also saved/restored the VRSAVE register, which isn't done
in the new entry path.
This means that the vrsave register is now volatile across guest exit,
which is an incorrect change in behaviour.
Fix this by saving/restoring the vrsave register in kvmhv_p9_guest_entry().
This restores the old, correct, behaviour.
Fixes: 95a6432ce9038 ("KVM: PPC: Book3S HV: Streamlined guest entry/exit path on P9 for radix guests")
Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail.com>
Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions