On Thu, Oct 22, 2020 at 06:31 AM -0400, Janosch Frank
wrote:
> Diag318 fencing needs to be determined on the current VM PV state and
> not on the state that the VM has when we create the CPU model.
>
> Signed-off-by: Janosch Frank
> Reported-by: Marc Hartmayer
> Fixes: fabdada935 ("s390: guest
On 22.10.20 12:31, Janosch Frank wrote:
> Diag318 fencing needs to be determined on the current VM PV state and
> not on the state that the VM has when we create the CPU model.
>
> Signed-off-by: Janosch Frank
> Reported-by: Marc Hartmayer
> Fixes: fabdada935 ("s390: guest support for diagnos
On 22.10.20 12:31, Janosch Frank wrote:
> Diag318 fencing needs to be determined on the current VM PV state and
> not on the state that the VM has when we create the CPU model.
>
> Signed-off-by: Janosch Frank
> Reported-by: Marc Hartmayer
> Fixes: fabdada935 ("s390: guest support for diagnose 0
Diag318 fencing needs to be determined on the current VM PV state and
not on the state that the VM has when we create the CPU model.
Signed-off-by: Janosch Frank
Reported-by: Marc Hartmayer
Fixes: fabdada935 ("s390: guest support for diagnose 0x318")
---
target/s390x/cpu_features.c | 5 +
t
