The sentence below refers to emulated device DMA. When emulated devices inside QEMU perform DMA goes through functions that keep the dirty page bitmap up to date. Likewise for CPU emulation performed by QEMU, which is not an issue if you are using KVM or other hypervisors supported by QEMU.
Whenever external code touches memory (which includes all the cases mentioned by Jason), it has to provide an interface for QEMU to read the dirty page bitmaps and synchronize them at appropriate points. Paolo On 18/03/20 16:13, Rob Miller wrote: > In trying to more fully understand DPT, I ran across an article > regarding how Physical RAM works within QEMU and noticed the statement > below. My current understanding, based upon the statement, is that DPT > is automatic inside QEMU. I can understand that this scheme is not > employed in all hypervisors, but i'm wondering if others, b/c of VM > migration, do have a similar scheme. > > > Dirty memory tracking > > When the guest CPU or device DMA stores to guest RAM this needs to be > noticed by several users: > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
