On 04/23/2017 07:47 PM, Aurelien Jarno wrote:
On 2017-04-23 19:38, Philippe Mathieu-Daudé wrote:
Hi Aurelien!
Why don't lock inside s390_virtio_hypercall() directly round the diag500
dispatch call?
s390_virtio_hypercall is shared between TCG and KVM. For KVM the lock is
already done before ca
On 2017-04-23 19:38, Philippe Mathieu-Daudé wrote:
> Hi Aurelien!
>
> Why don't lock inside s390_virtio_hypercall() directly round the diag500
> dispatch call?
s390_virtio_hypercall is shared between TCG and KVM. For KVM the lock is
already done before calling s390_virtio_hypercall in kvm_arch_ha
Hi Aurelien!
Why don't lock inside s390_virtio_hypercall() directly round the diag500
dispatch call?
regards,
Phil.
On 04/23/2017 07:32 PM, Aurelien Jarno wrote:
s390_virtio_hypercall can trigger IO events and interrupts, most notably
when using virtio-ccw devices.
Reviewed-by: Alexander G
s390_virtio_hypercall can trigger IO events and interrupts, most notably
when using virtio-ccw devices.
Reviewed-by: Alexander Graf
Signed-off-by: Aurelien Jarno
---
target/s390x/misc_helper.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/target/s390x/misc_helper.c b/target/s390x/misc_h
