------- Comment From <email address hidden> 2017-11-23 10:10 EDT-------
Yes it was believed that perf events will eventually replace the kvm_stat. The KVM community has now a different opinion. The kvm_stat counter in debugfs have value and they can provide insights that the perf events will not have.
e.g. see QEMU commit
commit b763adf1a6b271f17f15ea31fae93d03e980d911
Author: Paolo Bonzini <email address hidden>
AuthorDate: Wed May 21 12:42:26 2014 +0200
Commit: Paolo Bonzini <email address hidden>
CommitDate: Wed May 21 17:56:37 2014 +0200
kvm_stat: allow choosing between tracepoints and old stats
The old stats contain information not available in the tracepoints.
By default, keep the old behavior, but allow choosing which set of stats
to present, or even both.
Inspired by a patch from Marcelo Tosatti.
Signed-off-by: Paolo Bonzini <email address hidden>
FWIW, there have been a lot of updates to kvm_stat in the last 2 years.
------- Comment From <email address hidden> 2017-11-23 10:10 EDT-------
Yes it was believed that perf events will eventually replace the kvm_stat. The KVM community has now a different opinion. The kvm_stat counter in debugfs have value and they can provide insights that the perf events will not have.
e.g. see QEMU commit
commit b763adf1a6b271f 17f15ea31fae93d 03e980d911
Author: Paolo Bonzini <email address hidden>
AuthorDate: Wed May 21 12:42:26 2014 +0200
Commit: Paolo Bonzini <email address hidden>
CommitDate: Wed May 21 17:56:37 2014 +0200
kvm_stat: allow choosing between tracepoints and old stats
The old stats contain information not available in the tracepoints.
By default, keep the old behavior, but allow choosing which set of stats
to present, or even both.
Inspired by a patch from Marcelo Tosatti.
Signed-off-by: Paolo Bonzini <email address hidden>
FWIW, there have been a lot of updates to kvm_stat in the last 2 years.