On 6/9/19 21:38, Brad Campbell wrote:
[email protected]:kvm_vm_ioctl type 0xc008ae67, arg 0x7ffe13b0c970 [email protected]:kvm_vm_ioctl type 0xc008ae67, arg 0x7ffe13b0c980 [email protected]:kvm_vm_ioctl type 0xc008ae67, arg 0x7ffe13b0c970
Does this look familiar to anyone?
Ugh. System timer. So with the timer interrupt removed and an added trace on IRQ > 0: qxl/guest-0: 79096403248: qxldd: DrvCopyBits [email protected]:kvm_vcpu_ioctl cpu_index 2, type 0xae80, arg (nil) [email protected]:qxl_ring_res_put 0 #res=1 [email protected]:kvm_run_exit cpu_index 2, reason 2 [email protected]:qxl_io_write 0 native addr=4 (QXL_IO_NOTIFY_OOM) val=0 size=1 async=0 [email protected]:qxl_spice_oom 0 [email protected]:kvm_vcpu_ioctl cpu_index 2, type 0xae80, arg (nil) [email protected]:qxl_ring_command_check 0 native [email protected]:qxl_ring_res_push 0 native s#=0 res#=1 last=0x7f3c0d44b6e0 notify=yes [email protected]:qxl_ring_res_push_rest 0 ring 1/8 [326,325] [email protected]:qxl_send_events 0 1 [email protected]:qxl_ring_cursor_check 0 native [email protected]:qxl_ring_command_check 0 native [email protected]:kvm_set_irq irq 11, level 1, status 1 [email protected]:kvm_run_exit cpu_index 1, reason 2 [email protected]:qxl_io_write 0 native addr=3 (QXL_IO_UPDATE_IRQ) val=0 size=1 async=0 [email protected]:kvm_set_irq irq 11, level 0, status 1 [email protected]:kvm_vcpu_ioctl cpu_index 1, type 0xae80, arg (nil) [email protected]:kvm_run_exit cpu_index 1, reason 2 [email protected]:qxl_io_write 0 native addr=3 (QXL_IO_UPDATE_IRQ) val=0 size=1 async=0 [email protected]:kvm_vcpu_ioctl cpu_index 1, type 0xae80, arg (nil) [email protected]:kvm_run_exit cpu_index 2, reason 2 [email protected]:qxl_io_write 0 native addr=0 (QXL_IO_NOTIFY_CMD) val=0 size=1 async=0 [email protected]:kvm_vcpu_ioctl cpu_index 2, type 0xae80, arg (nil) [email protected]:qxl_ring_cursor_check 0 native [email protected]:qxl_ring_command_check 0 native 79213750625 qxl-0/cmd: cmd @ 0x10000000104b598 draw: surface_id 0 type copy effect opaque src 100000001fecbf8 (id 9fe0870780 type 0 flags 0 width 1920 height 1080, fmt 8 flags 0 x 1920 y 1080 stride 7680 palette 0 data 100000001fecc28) area 1920x1080+0+0 rop 8 [email protected]:qxl_ring_command_get 0 native [email protected]:qxl_ring_command_check 0 native [email protected]:qxl_ring_cursor_check 0 native [email protected]:qxl_ring_command_check 0 native [email protected]:qxl_ring_command_req_notification 0 [email protected]:kvm_run_exit cpu_index 2, reason 2 [email protected]:qxl_io_write 0 native addr=7 (QXL_IO_LOG) val=0 size=1 async=0 [email protected]:qxl_io_log 0 qxldd: DrvCopyBits So if I'm not mistaken (for the nth time), we have KVM_RUN on cpu index 2 here: [email protected]:kvm_vcpu_ioctl cpu_index 2, type 0xae80, arg (nil) And it returns here : [email protected]:kvm_run_exit cpu_index 2, reason 2 Does that imply guest code is running for ~100ms on that vcpu? Brad -- An expert is a person who has found out by his own painful experience all the mistakes that one can make in a very narrow field. - Niels Bohr
