KVM: s390: provide logging for diagnose 0x500

We might need to debug some virtio things, so better have diagnose 500
logged.

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>

diff --git a/arch/s390/kvm/diag.c b/arch/s390/kvm/diag.c
index 1ea4095b67d729fb67c01b4be81ce8bb7efe4bcb..ce865bd4f81d9696e7c9907d7bcaedede8f7cf43 100644 (file)
--- a/arch/s390/kvm/diag.c
+++ b/arch/s390/kvm/diag.c
@@ -212,6 +212,11 @@ static int __diag_virtio_hypercall(struct kvm_vcpu *vcpu)
            (vcpu->run->s.regs.gprs[1] != KVM_S390_VIRTIO_CCW_NOTIFY))
                return -EOPNOTSUPP;
 
+       VCPU_EVENT(vcpu, 4, "diag 0x500 schid 0x%8.8x queue 0x%x cookie 0x%llx",
+                           (u32) vcpu->run->s.regs.gprs[2],
+                           (u32) vcpu->run->s.regs.gprs[3],
+                           vcpu->run->s.regs.gprs[4]);
+
        /*
         * The layout is as follows:
         * - gpr 2 contains the subchannel id (passed as addr)