pkvm: Prefix metrics when running on A0 chip

A0 and B0 chips have different performance characteristics when it comes
to the hypervisor because B0 waits for SysMMU_SYNCs to complete during
every memory ownership transaction.

Set debug.hypervisor.metrics_tag=hwrev_a0 on PROTO1.x and EVT1.0
devices. EVT1.1 and later are B0 and benchmarks are representative of
production devices. This is only done on userdebug/eng builds.

Test: 'getprop | grep hypervisor' on A0/B0 devices
Change-Id: I0c81a0e4706a13cd63358de23048087a9190b9da
This commit is contained in:
David Brazdil 2022-09-24 00:43:41 +01:00 committed by TreeHugger Robot
parent 80fb216437
commit a9b460cfe9

View file

@ -32,3 +32,12 @@ on post-fs-data
chown bluetooth system /dev/logbuffer_btlpm
chown bluetooth system /dev/logbuffer_btpower
chown bluetooth system /dev/logbuffer_tty18
# pKVM performance is different on A0 and B0 chips.
# Add extra tag to metrics collected on A0 to separate the results.
on property:ro.revision=PROTO1.0
setprop debug.hypervisor.metrics_tag "hwrev_a0"
on property:ro.revision=PROTO1.1
setprop debug.hypervisor.metrics_tag "hwrev_a0"
on property:ro.revision=EVT1.0
setprop debug.hypervisor.metrics_tag "hwrev_a0"