On Tue, 15 Aug 2017 14:04:09 +1000
David Gibson wrote:
> On Mon, Aug 14, 2017 at 07:49:16PM +0200, Greg Kurz wrote:
> > When running in KVM PR mode, kvmppc_set_compat() always fail because the
> > current PR implementation doesn't handle KVM_REG_PPC_ARCH_COMPAT. Now that
> > the machine code inco
On Tue, 15 Aug 2017 11:40:34 +1000
Suraj Jitindar Singh wrote:
> On Mon, 2017-08-14 at 19:49 +0200, Greg Kurz wrote:
> > When running in KVM PR mode, kvmppc_set_compat() always fail because
> > the
> > current PR implementation doesn't handle KVM_REG_PPC_ARCH_COMPAT. Now
> > that
> > the machine
On Mon, Aug 14, 2017 at 07:49:16PM +0200, Greg Kurz wrote:
> When running in KVM PR mode, kvmppc_set_compat() always fail because the
> current PR implementation doesn't handle KVM_REG_PPC_ARCH_COMPAT. Now that
> the machine code inconditionally calls ppc_set_compat_all() at reset time
> to restore
On Mon, 2017-08-14 at 19:49 +0200, Greg Kurz wrote:
> When running in KVM PR mode, kvmppc_set_compat() always fail because
> the
> current PR implementation doesn't handle KVM_REG_PPC_ARCH_COMPAT. Now
> that
> the machine code inconditionally calls ppc_set_compat_all() at reset
> time
> to restore
When running in KVM PR mode, kvmppc_set_compat() always fail because the
current PR implementation doesn't handle KVM_REG_PPC_ARCH_COMPAT. Now that
the machine code inconditionally calls ppc_set_compat_all() at reset time
to restore the compat mode default value (commit 66d5c492dd3a9), it is
imposs