On Fri, 2023-02-10 at 14:54 +0000, Paul Durrant wrote: > > Given that this patch only provides a command to inject an event on a > specific port, I think it's be useful to have the target field report > the type of a VIRQ. PV drivers often hook VIRQ_DEBUG for dumping debug > info, so knowing which of the VIRQ ports
It's there in type_val, Wary of overengineering I hadn't actually translated it to strings but frankly if you don't know VIRQ_DEBUG is 1 you don't deserve to play... (qemu) xen-event-list port 1: vcpu: 0 interdomain(qemu:2) port 2: vcpu: 0 virq(0) port 3: vcpu: 0 ipi port 4: vcpu: 0 ipi port 5: vcpu: 0 virq(1) port 6: vcpu: 0 ipi port 7: vcpu: 0 ipi MASKED port 8: vcpu: 1 virq(0) port 9: vcpu: 1 ipi port 10: vcpu: 1 ipi port 11: vcpu: 1 virq(1) port 12: vcpu: 1 ipi port 13: vcpu: 1 ipi PENDING MASKED port 14: vcpu: 1 pirq(16) port 15: vcpu: 1 interdomain(qemu:3) port 16: vcpu: 0 pirq(22) port 17: vcpu: 1 pirq(18) port 18: vcpu: 0 pirq(17) port 19: vcpu: 1 pirq(20) port 20: vcpu: 0 pirq(19) (qemu) xen-event-inject 5 Delivered port 5 (qemu) [ 26.555560] [ 26.555560] vcpu 0 [ 26.555560] [ 26.555592] 0: masked=0 pending=0 event_sel 0000000000000000 [ 26.555592] [ 26.556526] 1: masked=0 pending=0 event_sel 0000000000000000 [ 26.556526] [ 26.557537] [ 26.557537] pending: [ 26.557537] [ 26.558514] 0000000000000000 [ 26.559242] 0000000000000000 ...
smime.p7s
Description: S/MIME cryptographic signature
