Thanks, applied.
On Fri, Aug 10, 2012 at 2:45 PM, Igor Mitsyanko wrote:
> For each newly created RAM block, dirty bitmap is reallocated with g_realloc,
> which doesn't
> make any promises on initial content of new extra data in returned buffer. In
> theory,
> we initialize this new data with cp
For each newly created RAM block, dirty bitmap is reallocated with g_realloc,
which doesn't
make any promises on initial content of new extra data in returned buffer. In
theory,
we initialize this new data with cpu_physical_memory_set_dirty_range() call. The
problem is, cpu_physical_memory_set_di
