diff options
| author | Jing Zhang <jingzhangos@google.com> | 2021-10-09 05:12:08 +0300 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2021-12-08 12:24:52 +0300 |
| commit | c3858335c711569b82a234a560dc19247e8f3fcc (patch) | |
| tree | 2c4e6688e22372a5da0e8209a7799c16bee890b0 /certs | |
| parent | fac4268894394213127e43856f41d10f29131e69 (diff) | |
| download | linux-c3858335c711569b82a234a560dc19247e8f3fcc.tar.xz | |
KVM: stats: Add stat to detect if vcpu is currently blocking
Add a "blocking" stat that userspace can use to detect the case where a
vCPU is not being run because of an vCPU/guest action, e.g. HLT or WFS on
x86, WFI on arm64, etc... Current guest/host/halt stats don't show this
well, e.g. if a guest halts for a long period of time then the vCPU could
could appear pathologically blocked due to a host condition, when in
reality the vCPU has been put into a not-runnable state by the guest.
Originally-by: Cannon Matthews <cannonmatthews@google.com>
Suggested-by: Sean Christopherson <seanjc@google.com>
Reviewed-by: David Matlack <dmatlack@google.com>
Signed-off-by: Jing Zhang <jingzhangos@google.com>
[sean: renamed stat to "blocking", massaged changelog]
Signed-off-by: Sean Christopherson <seanjc@google.com>
Message-Id: <20211009021236.4122790-16-seanjc@google.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions