On 02/14/2012 05:13 PM, Jan Kiszka wrote: > Note that KVM without in-kernel irqchip will report the address after > the instruction that triggered a write access. In contrast, read > accesses will return the precise information. > Well this is wierd. We could retro-doc one or the other behaviour, but this-on-read-but-that-on-write is just too strange. The documented way of dealing with this is to queue a signal and reenter the guest. kvm will perform anything it needs to complete the instruction (perhaps issuing more mmio, say if someone used movsd to read the APIC) and then exit on the signal. By then rip will point exactly after the instruction. -- 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
