On 11/10/2010 10:21 AM, Huang Ying wrote:
On Wed, 2010-11-10 at 14:56 +0800, Avi Kivity wrote: > On 11/08/2010 05:39 AM, Anthony Liguori wrote: > >> Yes. The main usage of the interface is automated testing. > > > > That's precisely what the command should not be used for. > > > > You can't assume a gpa -> hva mapping is consistent in an external > > application. If you want to implement an interface for testing, you > > have to push more of the logic into QEMU to avoid the race. > > An alternative is to use -mempath. Does poisoning work for tmpfs? Sorry for my stupid question.
It is not a stupid question.
Why the gpa -> hva mapping is not consistent for RAM if -mempath is not used?
Video RAM in the range a0000-bffff and PCI mapped RAM can change gpas (while remaining in the same hva).
Even for ordinary RAM, which doesn't normally change gpa/hva, I'm not sure we want to guarantee that it won't.
-- 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
