On 08/22/2012 03:47 PM, Xiao Guangrong wrote: > On 08/22/2012 08:06 PM, Avi Kivity wrote: >> On 08/21/2012 06:03 AM, Xiao Guangrong wrote: >>> Introduce write_readonly_mem in mmio-exit-info to indicate this exit is >>> caused by write access on readonly memslot >> >> Please document this in chapter 5 of apic.txt. >> > > Okay, please review this one. > > Subject: [PATCH v6 12/12] KVM: indicate readonly access fault > > Introduce write_readonly_mem in mmio-exit-info to indicate this exit is > caused by write access on readonly memslot > I'm not sure whether this indication can be trusted by userspace. By the time userspace gets to process this, the slot may no longer exist, or it may be writable. (in the same way an mmio exit might actually hit RAM) -- 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
