arm/arm64: KVM: Get rid of KVM_MEMSLOT_INCOHERENT
KVM_MEMSLOT_INCOHERENT is not used anymore, as we've killed its only use in the arm/arm64 MMU code. Let's remove the last artifacts. Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
This commit is contained in:
@@ -1876,15 +1876,6 @@ void kvm_arch_free_memslot(struct kvm *kvm, struct kvm_memory_slot *free,
|
|||||||
int kvm_arch_create_memslot(struct kvm *kvm, struct kvm_memory_slot *slot,
|
int kvm_arch_create_memslot(struct kvm *kvm, struct kvm_memory_slot *slot,
|
||||||
unsigned long npages)
|
unsigned long npages)
|
||||||
{
|
{
|
||||||
/*
|
|
||||||
* Readonly memslots are not incoherent with the caches by definition,
|
|
||||||
* but in practice, they are used mostly to emulate ROMs or NOR flashes
|
|
||||||
* that the guest may consider devices and hence map as uncached.
|
|
||||||
* To prevent incoherency issues in these cases, tag all readonly
|
|
||||||
* regions as incoherent.
|
|
||||||
*/
|
|
||||||
if (slot->flags & KVM_MEM_READONLY)
|
|
||||||
slot->flags |= KVM_MEMSLOT_INCOHERENT;
|
|
||||||
return 0;
|
return 0;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|||||||
@@ -45,7 +45,6 @@
|
|||||||
* include/linux/kvm_h.
|
* include/linux/kvm_h.
|
||||||
*/
|
*/
|
||||||
#define KVM_MEMSLOT_INVALID (1UL << 16)
|
#define KVM_MEMSLOT_INVALID (1UL << 16)
|
||||||
#define KVM_MEMSLOT_INCOHERENT (1UL << 17)
|
|
||||||
|
|
||||||
/* Two fragments for cross MMIO pages. */
|
/* Two fragments for cross MMIO pages. */
|
||||||
#define KVM_MAX_MMIO_FRAGMENTS 2
|
#define KVM_MAX_MMIO_FRAGMENTS 2
|
||||||
|
|||||||
Reference in New Issue
Block a user