Searched hist:"6502 a34cfd6695929086187f63fe670cc3050e68" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/arch/s390/kvm/ |
| H A D | intercept.c | diff 6502a34cfd6695929086187f63fe670cc3050e68 Tue Jun 21 07:19:51 CDT 2016 David Hildenbrand <dahi@linux.vnet.ibm.com> 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.
Acked-by: Janosch Frank <frankja@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
|
| H A D | kvm-s390.c | diff 6502a34cfd6695929086187f63fe670cc3050e68 Tue Jun 21 07:19:51 CDT 2016 David Hildenbrand <dahi@linux.vnet.ibm.com> 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.
Acked-by: Janosch Frank <frankja@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
|
| /openbmc/linux/arch/s390/include/asm/ |
| H A D | kvm_host.h | diff 6502a34cfd6695929086187f63fe670cc3050e68 Tue Jun 21 07:19:51 CDT 2016 David Hildenbrand <dahi@linux.vnet.ibm.com> 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.
Acked-by: Janosch Frank <frankja@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | kvm.h | diff 6502a34cfd6695929086187f63fe670cc3050e68 Tue Jun 21 07:19:51 CDT 2016 David Hildenbrand <dahi@linux.vnet.ibm.com> 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.
Acked-by: Janosch Frank <frankja@linux.vnet.ibm.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
|