On Tue, 20 Apr 2021 14:08:25 +0100, Yoan Picchi <yoan.picchi@xxxxxxx> wrote: > > This counter is meant to detect when the guest vm exits due to an > interrupt. Those interrupts might be unrelated to the guest VM (say, some > network packet arrived, and such) but they still trigger an exit which is > recorded by the "exit" counter. The main purpose of this counter is to > give some more granularity to this base exit counter so that one can have > a rough idea of where those exits comes from and so, if those general > exits happen because of the host or of the guest. I don't think this makes much sense. Why should we account interrupts for the guest when the interrupts don't have anything to do with it? And guess what, they almost *never* do. The only interrupt that could be accountable to the vcpu is the vPE doorbell, and that one can never causes an exit, by definition. The kernel already provides quite a lot around interrupt accounting already, and I don't think we need to do add more for the guest. If this made any sense, it should be applicable to any userspace task, not just vcpus. Thanks, M. -- Without deviation from the norm, progress is not possible. _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
