Decription:
KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started.
The patches to fix this have already been picked for jammy/master-next:
812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART"
435d17955519 "KVM: s390: Add a routine for setting userspace CPU state"
4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling"
For Ubuntu 20.04 the focal/master-next already contains:
d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART
so we additionally need the following two upstream commits in focal
67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state
8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling
Decription:
KVM: SIGP RESTART is reporting a CPU state 'stopped' after SIGP RESTART was issued, while it should report a 'busy' condition until the CPU is really started.
The patches to fix this have already been picked for jammy/master-next:
812de04661c4 "KVM: s390: Clarify SIGP orders versus STOP/RESTART"
435d17955519 "KVM: s390: Add a routine for setting userspace CPU state"
4563bcad46bf "KVM: s390: Simplify SIGP Set Arch handling"
For Ubuntu 20.04 the focal/master-next already contains:
d74b0d2d38d3 KVM: s390: Clarify SIGP orders versus STOP/RESTART
so we additionally need the following two upstream commits in focal
67cf68b6a5cc KVM: s390: Add a routine for setting userspace CPU state
8eeba194a32e KVM: s390: Simplify SIGP Set Arch handling