History

KVM: s390: allow user space to handle instr 0x0000

We will use illegal instruction 0x0000 for handling 2 byte sw breakpoints from user space. As it can be enabled dynamically via a capability, let's move setting of ICTL_OPEREXC to the post creation step, so we avoid any races when enabling that capability just while adding new cpus.

David Hildenbrand committed 10 years ago

Commit 6502a341 parent af1bae55 files · +43 −2Browse files

Showing the changes to include/uapi/linux (1 of 5 files). Show all

Unified · Split

include/uapi/linux/kvm.h+1−0
@@ -867,6 +867,7 @@ struct kvm_ppc_smmu_info { · 866 unmodified lines
867#define KVM_CAP_VCPU_ATTRIBUTES 127867#define KVM_CAP_VCPU_ATTRIBUTES 127
868#define KVM_CAP_MAX_VCPU_ID 128868#define KVM_CAP_MAX_VCPU_ID 128
869#define KVM_CAP_X2APIC_API 129869#define KVM_CAP_X2APIC_API 129
870#define KVM_CAP_S390_USER_INSTR0 130
870 871
871#ifdef KVM_CAP_IRQ_ROUTING872#ifdef KVM_CAP_IRQ_ROUTING
872 873

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t