Re: [PATCH] kvm: Fix memory slot page alignment logic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 10/11/2014 14:16, Alexander Graf wrote:
> No, because in that case you would map something as RAM that really
> isn't RAM.
> 
> Imagine you have the following memory layout:
> 
> 0x1000 page size
> 
> 1) 0x00000 - 0x10000 RAM
> 2) 0x10000 - 0x10100 MMIO
> 3) 0x10100 - 0x20000 RAM
> 
> Then you want to map 1) as memory slot and 4) from 0x11000 onwards as
> memory slot.
> 
> You can't map the page from 0x10000 - 0x11000 as memory slot, because
> part of it is MMIO.

Right.  The partial RAM page remains marked as MMIO as far as KVM is
concerned, so accesses are slow and you cannot run code from it.
However, it is fundamental that MMIO areas are not marked as RAM.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux