diff options
author | Kunkun Jiang <jiangkunkun@huawei.com> | 2024-11-07 13:41:36 -0800 |
---|---|---|
committer | Oliver Upton <oliver.upton@linux.dev> | 2024-11-11 19:52:31 +0000 |
commit | e9649129d33dca561305fc590a7c4ba8c3e5675a (patch) | |
tree | e8e4c1f32e87721d9cbb2377ccd1100d03eb28de /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | 7fe28d7e68f92cc3d0668b8f2fbdf5c303ac3022 (diff) | |
download | linux-stable-e9649129d33dca561305fc590a7c4ba8c3e5675a.tar.gz linux-stable-e9649129d33dca561305fc590a7c4ba8c3e5675a.tar.bz2 linux-stable-e9649129d33dca561305fc590a7c4ba8c3e5675a.zip |
KVM: arm64: vgic-its: Clear DTE when MAPD unmaps a device
vgic_its_save_device_tables will traverse its->device_list to
save DTE for each device. vgic_its_restore_device_tables will
traverse each entry of device table and check if it is valid.
Restore if valid.
But when MAPD unmaps a device, it does not invalidate the
corresponding DTE. In the scenario of continuous saves
and restores, there may be a situation where a device's DTE
is not saved but is restored. This is unreasonable and may
cause restore to fail. This patch clears the corresponding
DTE when MAPD unmaps a device.
Cc: stable@vger.kernel.org
Fixes: 57a9a117154c ("KVM: arm64: vgic-its: Device table save/restore")
Co-developed-by: Shusen Li <lishusen2@huawei.com>
Signed-off-by: Shusen Li <lishusen2@huawei.com>
Signed-off-by: Kunkun Jiang <jiangkunkun@huawei.com>
[Jing: Update with entry write helper]
Signed-off-by: Jing Zhang <jingzhangos@google.com>
Link: https://lore.kernel.org/r/20241107214137.428439-5-jingzhangos@google.com
Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions