interrupt total rate type vmcmd kills 17984 0 misc vmcmd extends 17980 0 misc vmcmd calls 185033 0 misc pserialize exclusive access 145 0 misc vmem static_bt_inuse 200 0 misc vmem static_bt_count 200 0 misc rndpseudo open soft 39 0 misc TLB shootdown 50603277 139 intr softint net/0 33488890 92 misc softint bio/0 1 0 misc softint clk/0 4239404 11 misc softint ser/0 2656 0 misc callout late/0 199 0 misc crosscall unicast 60 0 misc namecache entries collected 940528 2 misc namecache under scan target 362220 0 misc vcpu0 xenev0 channel 4 18112410 50 intr softint net/1 564465 1 misc softint bio/1 1 0 misc ... softint clk/11 385635 1 misc softint ser/11 149 0 misc callout late/11 1 0 misc vcpu0 xenev0 channel 2 297 0 intr vcpu0 raw systime went backwards 158 0 intr vcpu0 xenev0 channel 5 36222558 99 intr vcpu1 xenev0 channel 6 155497 0 intr vcpu1 missed hardclock 83 0 intr vcpu1 xenev0 channel 7 36222475 99 intr vcpu2 xenev0 channel 8 15438790 42 intr ... xbd0 map unaligned 96051 0 misc xbd1 map unaligned 1406926 3 miscTLB shootdown is there as some crosscall unicast. I don't see any other IPIs though.
Frank On 03/10/20 19:52, Manuel Bouyer wrote:
On Tue, Mar 10, 2020 at 07:30:33PM +0100, Frank Kardel wrote:No information about IPI in vmstat -i in DOM0 and DOMU.the dom0 is not MP so I don't expect to see IPIs here. But the domU is, so there should be IPIs here. Hum, it looks like IPIs are in vmstat -e, not -i ... sorryOtherwise it is usually responsive. Sometimes things get stuck but switching a screen in screen seems to unstick things. It seems like "wakeups" get sometimes lost.I guess it could be related to IPIs. But I'm running daily tests on domUs and I didn't notice anything strange