Skip to contentSkip to conversation

KVM: s390: Toggle operation exception for userspace

PATCH In review Eric Farman 5 participants 16 messages May 7 – May 11

Subsystems (5)
Documentation KVM Kselftest s390 +1 more subsystems
lore
Share & tools
lore
#0 lore raw

v2 cover KVM: s390: Toggle operation exception for userspace

Claudio, et al,

Here's an update to the USER_OPEREXEC patch I'd sent the other day. Besides the addition of Claudio's r-b (thank you!), Patch 1 is identical.

Patch 2 contains a couple of new selftests. As it stands, they all run with patch 1 applied, but I put the failing test at the end for if Patch 1 is missing.

Patch 3 is unrelated, but is a minor typo I stumbled on yesterday while looking at this. It seems small enough that a second git send-email command seems unnecessary. :)

Eric Farman (3):
KVM: s390: Toggle operation exception for userspace
KVM: s390: selftests: Extended user_operexec tests
KVM: s390: Fix typo in UCONTROL documentation

 Documentation/virt/kvm/api.rst                |   2 +-
 arch/s390/kvm/kvm-s390.c                      |   3 +-
 .../selftests/kvm/include/s390/facility.h     |   6 +
 .../selftests/kvm/s390/user_operexec.c        | 110 ++++++++++++++++++
 4 files changed, 119 insertions(+), 2 deletions(-)
Signature · 1 line
2.51.0
#1 lore raw

PATCH v2 1/3 KVM: s390: Toggle operation exception for userspace

The KVM_CAP_S390_USER_OPEREXEC capability allows operation exceptions to be forwarded to userspace. But the actual enablement at the hardware level occurs in kvm_arch_vcpu_postcreate(), and only if STFLE.74 or user_instr0 are enabled. The latter is associated with a separate capability (KVM_CAP_S390_USER_INSTR0), so the only way this happens for the USER_OPEREXEC capability is if STFLE.74 is enabled. KVM unconditionally enables this bit in kvm_arch_init_vm(), but the guest could disable it from the CPU model and thus ignore this capability.

Add USER_OPEREXEC to the check in kvm_arch_vcpu_postcreate(), such that either capability would enable this type of exception.

Fixes 8e8678e740ec ("KVM: s390: Add capability that forwards operation exceptions")
---
 arch/s390/kvm/kvm-s390.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
arch/s390/kvm/kvm-s390.c +2 -1
index e09960c2e6ed..a91a42174302 100644
@@ -3521,7 +3521,8 @@ void kvm_arch_vcpu_postcreate(struct kvm_vcpu *vcpu)
 		vcpu->arch.gmap = vcpu->kvm->arch.gmap;
 		sca_add_vcpu(vcpu);
 	}
-	if (test_kvm_facility(vcpu->kvm, 74) || vcpu->kvm->arch.user_instr0)
+	if (test_kvm_facility(vcpu->kvm, 74) || vcpu->kvm->arch.user_instr0 ||
+	    vcpu->kvm->arch.user_operexec)
 		vcpu->arch.sie_block->ictl |= ICTL_OPEREXC;
 }
 
Signature · 1 line
2.51.0
maintainer Reviewed-by on v2 1/3
#2 lore raw

Am 07.05.26 um 22:08 schrieb Eric Farman:

Quoted 9 lines

The KVM_CAP_S390_USER_OPEREXEC capability allows operation exceptions to be forwarded to userspace. But the actual enablement at the hardware level occurs in kvm_arch_vcpu_postcreate(), and only if STFLE.74 or user_instr0 are enabled. The latter is associated with a separate capability (KVM_CAP_S390_USER_INSTR0), so the only way this happens for the USER_OPEREXEC capability is if STFLE.74 is enabled. KVM unconditionally enables this bit in kvm_arch_init_vm(), but the guest could disable it from the CPU model and thus ignore this capability.

Quoted 6 lines

Add USER_OPEREXEC to the check in kvm_arch_vcpu_postcreate(), such that either capability would enable this type of exception.

Fixes 8e8678e740ec ("KVM: s390: Add capability that forwards operation exceptions")
Quoted 18 lines
---
  arch/s390/kvm/kvm-s390.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)
arch/s390/kvm/kvm-s390.c +2 -1
index e09960c2e6ed..a91a42174302 100644
@@ -3521,7 +3521,8 @@ void kvm_arch_vcpu_postcreate(struct kvm_vcpu *vcpu)
  		vcpu->arch.gmap = vcpu->kvm->arch.gmap;
  		sca_add_vcpu(vcpu);
  	}
-	if (test_kvm_facility(vcpu->kvm, 74) || vcpu->kvm->arch.user_instr0)
+	if (test_kvm_facility(vcpu->kvm, 74) || vcpu->kvm->arch.user_instr0 ||
+	    vcpu->kvm->arch.user_operexec)
  		vcpu->arch.sie_block->ictl |= ICTL_OPEREXC;
  }
 
maintainer Reviewed-by on v2 1/3
#3 lore raw
In reply to Eric Farman
Quoted 9 lines · Eric Farman

The KVM_CAP_S390_USER_OPEREXEC capability allows operation exceptions to be forwarded to userspace. But the actual enablement at the hardware level occurs in kvm_arch_vcpu_postcreate(), and only if STFLE.74 or user_instr0 are enabled. The latter is associated with a separate capability (KVM_CAP_S390_USER_INSTR0), so the only way this happens for the USER_OPEREXEC capability is if STFLE.74 is enabled. KVM unconditionally enables this bit in kvm_arch_init_vm(), but the guest could disable it from the CPU model and thus ignore this capability.

Quoted 6 lines

Add USER_OPEREXEC to the check in kvm_arch_vcpu_postcreate(), such that either capability would enable this type of exception.

Fixes 8e8678e740ec ("KVM: s390: Add capability that forwards operation exceptions")

It boggles my mind that I missed this, sigh

Quoted 18 lines
---
  arch/s390/kvm/kvm-s390.c | 3 ++-
  1 file changed, 2 insertions(+), 1 deletion(-)
arch/s390/kvm/kvm-s390.c +2 -1
index e09960c2e6ed..a91a42174302 100644
@@ -3521,7 +3521,8 @@ void kvm_arch_vcpu_postcreate(struct kvm_vcpu *vcpu)
  		vcpu->arch.gmap = vcpu->kvm->arch.gmap;
  		sca_add_vcpu(vcpu);
  	}
-	if (test_kvm_facility(vcpu->kvm, 74) || vcpu->kvm->arch.user_instr0)
+	if (test_kvm_facility(vcpu->kvm, 74) || vcpu->kvm->arch.user_instr0 ||
+	    vcpu->kvm->arch.user_operexec)
  		vcpu->arch.sie_block->ictl |= ICTL_OPEREXC;
  }
 
maintainer
#4 lore raw
In reply to Eric Farman
Quoted 9 lines · Eric Farman

The KVM_CAP_S390_USER_OPEREXEC capability allows operation exceptions to be forwarded to userspace. But the actual enablement at the hardware level occurs in kvm_arch_vcpu_postcreate(), and only if STFLE.74 or user_instr0 are enabled. The latter is associated with a separate capability (KVM_CAP_S390_USER_INSTR0), so the only way this happens for the USER_OPEREXEC capability is if STFLE.74 is enabled. KVM unconditionally enables this bit in kvm_arch_init_vm(), but the guest could disable it from the CPU model and thus ignore this capability.

Quoted 3 lines

Add USER_OPEREXEC to the check in kvm_arch_vcpu_postcreate(), such that either capability would enable this type of exception.

Naming wise shouldn't this be something like:
KVM: s390: Fix S390_USER_OPEREXEC enablement without stfle 74

?

#5 lore raw
Quoted 10 lines · Janosch Frank
Quoted 9 lines · Eric Farman

The KVM_CAP_S390_USER_OPEREXEC capability allows operation exceptions to be forwarded to userspace. But the actual enablement at the hardware level occurs in kvm_arch_vcpu_postcreate(), and only if STFLE.74 or user_instr0 are enabled. The latter is associated with a separate capability (KVM_CAP_S390_USER_INSTR0), so the only way this happens for the USER_OPEREXEC capability is if STFLE.74 is enabled. KVM unconditionally enables this bit in kvm_arch_init_vm(), but the guest could disable it from the CPU model and thus ignore this capability.

Quoted 8 lines
Quoted 3 lines

Add USER_OPEREXEC to the check in kvm_arch_vcpu_postcreate(), such that either capability would enable this type of exception.

Naming wise shouldn't this be something like:
KVM: s390: Fix S390_USER_OPEREXEC enablement without stfle 74

?

Yeah, that is clearer, and I would be fine with that edit.

#6 lore raw

PATCH v2 2/3 KVM: s390: selftests: Extended user_operexec tests

In reply to Eric Farman

There is a possibility that the user_operexec capability only works if facility bit 74 is enabled. This is now fixed, but add a selftest to demonstrate that.

---
 .../selftests/kvm/include/s390/facility.h     |   6 +
 .../selftests/kvm/s390/user_operexec.c        | 110 ++++++++++++++++++
 2 files changed, 116 insertions(+)
tools/testing/selftests/kvm/include/s390/facility.h +6 -0
index 41a265742666..e5259f63be22 100644
@@ -11,6 +11,7 @@
 #ifndef SELFTEST_KVM_FACILITY_H
 #define SELFTEST_KVM_FACILITY_H
 
+#include <linux/atomic.h>
 #include <linux/bitops.h>
 
 /* alt_stfle_fac_list[16] + stfle_fac_list[16] */
@@ -19,6 +20,11 @@
 extern u64 stfl_doublewords[NB_STFL_DOUBLEWORDS];
 extern bool stfle_flag;
 
+static inline bool clear_bit_inv(unsigned long nr, unsigned long *ptr)
+{
+	return clear_bit(nr ^ (BITS_PER_LONG - 1), ptr);
+}
+
 static inline bool test_bit_inv(unsigned long nr, const unsigned long *ptr)
 {
 	return test_bit(nr ^ (BITS_PER_LONG - 1), ptr);
tools/testing/selftests/kvm/s390/user_operexec.c +110 -0

128 lines not on this page · raw message

Signature · 1 line
2.51.0
#7 lore raw

Re: [PATCH v2 2/3] KVM: s390: selftests: Extended user_operexec tests

Am 07.05.26 um 22:08 schrieb Eric Farman:

Quoted 5 lines

There is a possibility that the user_operexec capability only works if facility bit 74 is enabled. This is now fixed, but add a selftest to demonstrate that.

looks sane to me

Christian Borntraeger <[email protected]>

maintainer Reviewed-by on v2 2/3
#8 lore raw

Re: [PATCH v2 2/3] KVM: s390: selftests: Extended user_operexec tests

In reply to Eric Farman
Quoted 5 lines · On Thu, 7 May 2026 22:08:35 +0200 Eric Farman <[email protected]> wrote:

There is a possibility that the user_operexec capability only works if facility bit 74 is enabled. This is now fixed, but add a selftest to demonstrate that.

Quoted 164 lines
---
 .../selftests/kvm/include/s390/facility.h     |   6 +
 .../selftests/kvm/s390/user_operexec.c        | 110 ++++++++++++++++++
 2 files changed, 116 insertions(+)
tools/testing/selftests/kvm/include/s390/facility.h +6 -0
index 41a265742666..e5259f63be22 100644
@@ -11,6 +11,7 @@
 #ifndef SELFTEST_KVM_FACILITY_H
 #define SELFTEST_KVM_FACILITY_H
 
+#include <linux/atomic.h>
 #include <linux/bitops.h>
 
 /* alt_stfle_fac_list[16] + stfle_fac_list[16] */
@@ -19,6 +20,11 @@
 extern u64 stfl_doublewords[NB_STFL_DOUBLEWORDS];
 extern bool stfle_flag;
 
+static inline bool clear_bit_inv(unsigned long nr, unsigned long *ptr)
+{
+	return clear_bit(nr ^ (BITS_PER_LONG - 1), ptr);
+}
+
 static inline bool test_bit_inv(unsigned long nr, const unsigned long *ptr)
 {
 	return test_bit(nr ^ (BITS_PER_LONG - 1), ptr);
tools/testing/selftests/kvm/s390/user_operexec.c +110 -0
index 714906c1d12a..b24c1f9dbbe8 100644
@@ -6,6 +6,7 @@
  * Authors:
  *  Janosch Frank <[email protected]>
  */
+#include "facility.h"
 #include "kselftest.h"
 #include "kvm_util.h"
 #include "test_util.h"
@@ -109,6 +110,111 @@ static void test_user_operexec_combined(void)
 	kvm_vm_free(vm);
 }
 
+static struct kvm_vm *create_vm_without_sthyi(void)
+{
+	struct kvm_s390_vm_cpu_processor info;
+	struct kvm_vm *vm;
+
+	vm = vm_create(1);
+
+	kvm_device_attr_get(vm->fd, KVM_S390_VM_CPU_MODEL,
+			    KVM_S390_VM_CPU_PROCESSOR, &info);
+
+	clear_bit_inv(74, (unsigned long *)&info.fac_list);
+	kvm_device_attr_set(vm->fd, KVM_S390_VM_CPU_MODEL,
+			    KVM_S390_VM_CPU_PROCESSOR, &info);
+
+	return vm;
+}
+
+static void test_user_instr0_no_stfle_74(void)
+{
+	struct kvm_vcpu *vcpu;
+	struct kvm_vm *vm;
+	int rc;
+
+	vm = create_vm_without_sthyi();
+
+	rc = __vm_enable_cap(vm, KVM_CAP_S390_USER_INSTR0, 0);
+	TEST_ASSERT_EQ(0, rc);
+
+	vcpu = vm_vcpu_add(vm, 0, guest_code_instr0);
+
+	vcpu_run(vcpu);
+	TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_S390_SIEIC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.icptcode, ICPT_OPEREXC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.ipa, 0x0000);
+
+	kvm_vm_free(vm);
+}
+
+static void test_user_operexec_no_stfle_74(void)
+{
+	struct kvm_vcpu *vcpu;
+	struct kvm_vm *vm;
+	int rc;
+
+	vm = create_vm_without_sthyi();
+
+	rc = __vm_enable_cap(vm, KVM_CAP_S390_USER_OPEREXEC, 0);
+	TEST_ASSERT_EQ(0, rc);
+
+	vcpu = vm_vcpu_add(vm, 0, guest_code_user_operexec);
+
+	vcpu_run(vcpu);
+	TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_S390_SIEIC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.icptcode, ICPT_OPEREXC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.ipa, 0x0807);
+
+	kvm_vm_free(vm);
+}
+
+static void test_instr0_combined_no_stfle_74(void)
+{
+	struct kvm_vcpu *vcpu;
+	struct kvm_vm *vm;
+	int rc;
+
+	vm = create_vm_without_sthyi();
+
+	rc = __vm_enable_cap(vm, KVM_CAP_S390_USER_INSTR0, 0);
+	TEST_ASSERT_EQ(0, rc);
+	rc = __vm_enable_cap(vm, KVM_CAP_S390_USER_OPEREXEC, 0);
+	TEST_ASSERT_EQ(0, rc);
+
+	vcpu = vm_vcpu_add(vm, 0, guest_code_instr0);
+
+	vcpu_run(vcpu);
+	TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_S390_SIEIC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.icptcode, ICPT_OPEREXC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.ipa, 0x0000);
+
+	kvm_vm_free(vm);
+}
+
+static void test_operexec_combined_no_stfle_74(void)
+{
+	struct kvm_vcpu *vcpu;
+	struct kvm_vm *vm;
+	int rc;
+
+	vm = create_vm_without_sthyi();
+
+	rc = __vm_enable_cap(vm, KVM_CAP_S390_USER_INSTR0, 0);
+	TEST_ASSERT_EQ(0, rc);
+	rc = __vm_enable_cap(vm, KVM_CAP_S390_USER_OPEREXEC, 0);
+	TEST_ASSERT_EQ(0, rc);
+
+	vcpu = vm_vcpu_add(vm, 0, guest_code_user_operexec);
+
+	vcpu_run(vcpu);
+	TEST_ASSERT_KVM_EXIT_REASON(vcpu, KVM_EXIT_S390_SIEIC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.icptcode, ICPT_OPEREXC);
+	TEST_ASSERT_EQ(vcpu->run->s390_sieic.ipa, 0x0807);
+
+	kvm_vm_free(vm);
+}
+
 /*
  * Run all tests above.
  *
@@ -122,6 +228,10 @@ static struct testdef {
 	{ "instr0", test_user_instr0 },
 	{ "operexec", test_user_operexec },
 	{ "operexec_combined", test_user_operexec_combined},
+	{ "instr0_no_stfle_74", test_user_instr0_no_stfle_74 },
+	{ "instr0_combined_no_stfle_74", test_instr0_combined_no_stfle_74 },
+	{ "operexec_combined_no_stfle_74", test_operexec_combined_no_stfle_74 },
+	{ "operexec_no_stfle_74", test_user_operexec_no_stfle_74 },
 };
 
 int main(int argc, char *argv[])
maintainer Acked-by on v2 2/3
#9 lore raw

Re: [PATCH v2 2/3] KVM: s390: selftests: Extended user_operexec tests

In reply to Eric Farman
Quoted 3 lines · Eric Farman

There is a possibility that the user_operexec capability only works if facility bit 74 is enabled. This is now fixed, but add a selftest to demonstrate that.

#10 lore raw

PATCH v2 3/3 KVM: s390: Fix typo in UCONTROL documentation

In reply to Eric Farman

Small typo noticed while writing the USER_OPEREXEC selftest.

---
 Documentation/virt/kvm/api.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/virt/kvm/api.rst +1 -1
index 52bbbb553ce1..f0eba90602f0 100644
@@ -6827,7 +6827,7 @@ s390 specific.
 		} s390_ucontrol;
 
 s390 specific. A page fault has occurred for a user controlled virtual
-machine (KVM_VM_S390_UNCONTROL) on its host page table that cannot be
+machine (KVM_VM_S390_UCONTROL) on its host page table that cannot be
 resolved by the kernel.
 The program code and the translation exception code that were placed
 in the cpu's lowcore are presented here as defined by the z Architecture
Signature · 1 line
2.51.0
maintainer Reviewed-by on v2 3/3
#11 lore raw

Re: [PATCH v2 3/3] KVM: s390: Fix typo in UCONTROL documentation

Quoted 3 lines · On Thu, 7 May 2026 22:08:36 +0200 Eric Farman <[email protected]> wrote:

Small typo noticed while writing the USER_OPEREXEC selftest.

Quoted 17 lines
---
 Documentation/virt/kvm/api.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/virt/kvm/api.rst +1 -1
index 52bbbb553ce1..f0eba90602f0 100644
@@ -6827,7 +6827,7 @@ s390 specific.
 		} s390_ucontrol;
 
 s390 specific. A page fault has occurred for a user controlled virtual
-machine (KVM_VM_S390_UNCONTROL) on its host page table that cannot be
+machine (KVM_VM_S390_UCONTROL) on its host page table that cannot be
 resolved by the kernel.
 The program code and the translation exception code that were placed
 in the cpu's lowcore are presented here as defined by the z Architecture
#13 lore raw
In reply to Eric Farman

Am 07.05.26 um 22:08 schrieb Eric Farman:

Quoted 18 lines

Claudio, et al,

Here's an update to the USER_OPEREXEC patch I'd sent the other day. Besides the addition of Claudio's r-b (thank you!), Patch 1 is identical.

Patch 2 contains a couple of new selftests. As it stands, they all run with patch 1 applied, but I put the failing test at the end for if Patch 1 is missing.

Patch 3 is unrelated, but is a minor typo I stumbled on yesterday while looking at this. It seems small enough that a second git send-email command seems unnecessary. :)

Eric Farman (3):
KVM: s390: Toggle operation exception for userspace
KVM: s390: selftests: Extended user_operexec tests
KVM: s390: Fix typo in UCONTROL documentation

Quoted 6 lines
  Documentation/virt/kvm/api.rst                |   2 +-
  arch/s390/kvm/kvm-s390.c                      |   3 +-
  .../selftests/kvm/include/s390/facility.h     |   6 +
  .../selftests/kvm/s390/user_operexec.c        | 110 ++++++++++++++++++
  4 files changed, 119 insertions(+), 2 deletions(-)

Independent from this series (which makes sense on its own)
shouldnt we add another fixup so that we send these kernel injects also to userspace?

git grep PGM_OPERATION linux/master arch/s390/kvm/
linux/master:arch/s390/kvm/intercept.c: return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/intercept.c: return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);

linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION)
#14 lore raw
Quoted 26 lines · Christian Borntraeger

Am 07.05.26 um 22:08 schrieb Eric Farman:

Quoted 18 lines

Claudio, et al,

Here's an update to the USER_OPEREXEC patch I'd sent the other day. Besides the addition of Claudio's r-b (thank you!), Patch 1 is identical.

Patch 2 contains a couple of new selftests. As it stands, they all run with patch 1 applied, but I put the failing test at the end for if Patch 1 is missing.

Patch 3 is unrelated, but is a minor typo I stumbled on yesterday while looking at this. It seems small enough that a second git send-email command seems unnecessary. :)

Eric Farman (3):
KVM: s390: Toggle operation exception for userspace
KVM: s390: selftests: Extended user_operexec tests
KVM: s390: Fix typo in UCONTROL documentation

Quoted 6 lines
  Documentation/virt/kvm/api.rst                |   2 +-
  arch/s390/kvm/kvm-s390.c                      |   3 +-
  .../selftests/kvm/include/s390/facility.h     |   6 +
  .../selftests/kvm/s390/user_operexec.c        | 110 ++++++++++++++++++
  4 files changed, 119 insertions(+), 2 deletions(-)
Quoted 3 lines

Independent from this series (which makes sense on its own)
shouldnt we add another fixup so that we send these kernel injects also to userspace?

Hrm, that's a reasonable idea for the ones in priv.c (intercept.c are already covered, see below). I'll see if I can find a way to unify (and test) them.

Quoted 3 lines

git grep PGM_OPERATION linux/master arch/s390/kvm/
linux/master:arch/s390/kvm/intercept.c: return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);

This is handle_sthyi(), called by handle_operexc(), if stfle.74 is not present.

Quoted 1 line

linux/master:arch/s390/kvm/intercept.c: return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);

This is handle_operexc(), if neither user_instr0 nor user_operexec are present.

Quoted 5 lines
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION);
linux/master:arch/s390/kvm/priv.c:              return kvm_s390_inject_program_int(vcpu, PGM_OPERATION)
#15 lore raw
In reply to Eric Farman

Am 07.05.26 um 22:08 schrieb Eric Farman:

Quoted 18 lines

Claudio, et al,

Here's an update to the USER_OPEREXEC patch I'd sent the other day. Besides the addition of Claudio's r-b (thank you!), Patch 1 is identical.

Patch 2 contains a couple of new selftests. As it stands, they all run with patch 1 applied, but I put the failing test at the end for if Patch 1 is missing.

Patch 3 is unrelated, but is a minor typo I stumbled on yesterday while looking at this. It seems small enough that a second git send-email command seems unnecessary. :)

Eric Farman (3):
KVM: s390: Toggle operation exception for userspace
KVM: s390: selftests: Extended user_operexec tests
KVM: s390: Fix typo in UCONTROL documentation

Quoted 5 lines
  Documentation/virt/kvm/api.rst                |   2 +-
  arch/s390/kvm/kvm-s390.c                      |   3 +-
  .../selftests/kvm/include/s390/facility.h     |   6 +
  .../selftests/kvm/s390/user_operexec.c        | 110 ++++++++++++++++++
  4 files changed, 119 insertions(+), 2 deletions(-)

I applied this series internally and queued for CI.