diff options
author | Alexey Kardashevskiy <aik@ozlabs.ru> | 2014-07-19 17:59:34 +1000 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2014-09-05 16:36:32 -0700 |
commit | d376ef4620b1d17e63c9878da6f88c0e5a890d9f (patch) | |
tree | 48b797c6d29969264df3ab82f572546675d7e728 /include/linux/cryptohash.h | |
parent | dd713bdfd1e1b4d7a33a3a6f91e5e9886d13af4b (diff) |
KVM: PPC: Book3S: Fix LPCR one_reg interface
commit a0840240c0c6bcbac8f0f5db11f95c19aaf9b52f upstream.
Unfortunately, the LPCR got defined as a 32-bit register in the
one_reg interface. This is unfortunate because KVM allows userspace
to control the DPFD (default prefetch depth) field, which is in the
upper 32 bits. The result is that DPFD always get set to 0, which
reduces performance in the guest.
We can't just change KVM_REG_PPC_LPCR to be a 64-bit register ID,
since that would break existing userspace binaries. Instead we define
a new KVM_REG_PPC_LPCR_64 id which is 64-bit. Userspace can still use
the old KVM_REG_PPC_LPCR id, but it now only modifies those fields in
the bottom 32 bits that userspace can modify (ILE, TC and AIL).
If userspace uses the new KVM_REG_PPC_LPCR_64 id, it can modify DPFD
as well.
Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'include/linux/cryptohash.h')
0 files changed, 0 insertions, 0 deletions