Re: [PATCH 16/22] KVM: MMU: Track page fault data in struct vcpu

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

 



On 04/27/2010 04:57 PM, Joerg Roedel wrote:

But the nested guest can use pae paging and generate a #NPF with
exit_info_2>  4GB.  So we need to keep the full fault address; if we
truncate, the guest might actually resolve the fault and let the
nested guest continue.
This could only be a malicious guest because it can't have memory above
4gb. But a guest could certainly setup its page tables to point there,
thats true. So I change it to u64.

It doesn't need to be malicious, for example it could set up an mmio PCI BAR outside the 4GB space.

--
error compiling committee.c: too many arguments to function

--
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