Re: [PATCH RFC 0/1] KVM: ioctl for reading/writing guest memory

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

 




On 03/02/2015 13:11, Thomas Huth wrote:
> The userspace (QEMU) then can simply call this ioctl when it wants
> to read or write from/to virtual guest memory. Then kernel then takes
> the IPTE-lock, walks the MMU table of the guest to find out the
> physical address that corresponds to the virtual address, copies
> the requested amount of bytes from the userspace buffer to guest
> memory or the other way round, and finally frees the IPTE-lock again.
> 
> Does that sound like a viable solution (IMHO it does ;-))? Or should
> I maybe try to pursue another approach?

It looks feasible to me as well.

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