On Mon, Nov 07, 2016 at 03:09:58PM +1100, Paul Mackerras wrote:
> When switching from/to a guest that has a transaction in progress,
> we need to save/restore the checkpointed register state. Although
> XER is part of the CPU state that gets checkpointed, the code that
> does this saving and restoring doesn't save/restore XER.
>
> This fixes it by saving and restoring the XER. To allow userspace
> to read/write the checkpointed XER value, we also add a new ONE_REG
> specifier.
>
> The visible effect of this bug is that the guest may see its XER
> value being corrupted when it uses transactions.
>
> Fixes: e4e38121507a ("KVM: PPC: Book3S HV: Add transactional memory support")
> Fixes: 0a8eccefcb34 ("KVM: PPC: Book3S HV: Add missing code for transaction reclaim on guest exit")
> Cc: stable@xxxxxxxxxxxxxxx # v3.15+
> Signed-off-by: Paul Mackerras <paulus@xxxxxxxxxx>
Applied to kvm-ppc-next.
Paul.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
