Hi Christoffer, >> >> These are for mapping host memory, not guest memory, right? > > yes (or to be exact - hypervisor memory). The point is that there are special hardware requirements for translation tables used in Hyp-mode not otherwise satisfied by the normal page tables. In function init_hyp_memory() you map some memory regions for vectors, vcpu, stack, etc. using function create_hyp_mappings. Just wondering, how do you make sure that guest will never map its own data into these addresses? Since guest is not para-virtualized, it can use any VA it wants, including these addresses. In your earlier KVM-arm paper you mentioned that such mappings were write-protected, so whenever guest tried to access them you needed to relocate such shared pages. Is the mechanism the same or you somehow take advantage of virtualization extensions to avoid this problem? Thanks, Alexey -- 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
