diff options
| author | Shaoqin Huang <shahuang@redhat.com> | 2024-07-23 03:20:00 -0400 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2024-08-25 17:48:43 +0100 |
| commit | ffe68b2d19a5a84440fea99a732cfc3b157559eb (patch) | |
| tree | e40e172c1748c6311b0293cf8a91749ecf1fa3e8 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | KVM: arm64: Make the exposed feature bits in AA64DFR0_EL1 writable from users... (diff) | |
| download | linux-ffe68b2d19a5a84440fea99a732cfc3b157559eb.tar.gz linux-ffe68b2d19a5a84440fea99a732cfc3b157559eb.zip | |
KVM: arm64: Disable fields that KVM doesn't know how to handle in ID_AA64PFR1_EL1
For some of the fields in the ID_AA64PFR1_EL1 register, KVM doesn't know
how to handle them right now. So explicitly disable them in the register
accessor, then those fields value will be masked to 0 even if on the
hardware the field value is 1. This is safe because from a UAPI point of
view that read_sanitised_ftr_reg() doesn't yet return a nonzero value
for any of those fields.
This will benifit the migration if the host and VM have different values
when restoring a VM.
Those fields include RNDR_trap, NMI, MTE_frac, GCS, THE, MTEX, DF2, PFAR.
Signed-off-by: Shaoqin Huang <shahuang@redhat.com>
Link: https://lore.kernel.org/r/20240723072004.1470688-2-shahuang@redhat.com
Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
