diff options
| author | Sean Christopherson <[email protected]> | 2021-10-08 19:12:09 -0700 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-12-08 04:24:52 -0500 |
| commit | 109a98260b533722d1190dcfa18447dd39fee5ff (patch) | |
| tree | dc9abf706ab963d37bc436c2401670dd4842de41 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | c3858335c711569b82a234a560dc19247e8f3fcc (diff) | |
KVM: Don't redo ktime_get() when calculating halt-polling stop/deadline
Calculate the halt-polling "stop" time using "start" instead of redoing
ktime_get(). In practice, the numbers involved are in the noise (e.g.,
in the happy case where hardware correctly predicts do_halt_poll and
there are no interrupts, "start" is probably only a few cycles old)
and either approach is perfectly ok. But it's more precise to count
any extra latency toward the halt-polling time.
Reviewed-by: David Matlack <[email protected]>
Signed-off-by: Sean Christopherson <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions