diff options
| author | Marc Zyngier <[email protected]> | 2024-03-21 17:37:06 +0000 |
|---|---|---|
| committer | Oliver Upton <[email protected]> | 2024-04-01 01:33:52 -0700 |
| commit | d96c66ab9fb3ad8b243669cf6b41e68d0f7f9ecd (patch) | |
| tree | 57d96338576cf95d3aed8afd9565d30e849dcf11 /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | b3320142f3db9b3f2a23460abd3e22292e1530a5 (diff) | |
KVM: arm64: Rationalise KVM banner output
We are not very consistent when it comes to displaying which mode
we're in (VHE, {n,h}VHE, protected or not). For example, booting
in protected mode with hVHE results in:
[ 0.969545] kvm [1]: Protected nVHE mode initialized successfully
which is mildly amusing considering that the machine is VHE only.
We already cleaned this up a bit with commit 1f3ca7023fe6 ("KVM:
arm64: print Hyp mode"), but that's still unsatisfactory.
Unify the three strings into one and use a mess of conditional
statements to sort it out (yes, it's a slow day).
Signed-off-by: Marc Zyngier <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Oliver Upton <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions