diff options
| author | Marc Zyngier <marc.zyngier@arm.com> | 2018-05-17 11:05:08 +0100 |
|---|---|---|
| committer | Marc Zyngier <marc.zyngier@arm.com> | 2018-07-09 11:37:41 +0100 |
| commit | 09605e94c2cbb67c6472c07e1c06a7a0e7271f83 (patch) | |
| tree | 07619151aabc42a82224d7ef09b48184745edb12 /virt/kvm/arm/mmu.c | |
| parent | e48d53a91f6e90873e21a5ca5e8c0d7a9f8936a4 (diff) | |
| download | linux-09605e94c2cbb67c6472c07e1c06a7a0e7271f83.tar.bz2 | |
arm64: KVM: Handle Set/Way CMOs as NOPs if FWB is present
Set/Way handling is one of the ugliest corners of KVM. We shouldn't
have to handle that, but better safe than sorry.
Thankfully, FWB fixes this for us by not requiering any maintenance
(the guest is forced to use cacheable memory, no matter what it says,
and the whole system is garanteed to be cache coherent), which means
we don't have to emulate S/W CMOs, and don't have to track VM ops either.
We still have to trap S/W though, if only to prevent the guest from
doing something bad.
Reviewed-by: Christoffer Dall <christoffer.dall@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt/kvm/arm/mmu.c')
0 files changed, 0 insertions, 0 deletions