On 08/14/2011 11:45 PM, Umesh Deshpande wrote:
That's not too good because qemu_get_ram_ptr is a hot path for TCG.
Looks like qemu_get_ram_ptr isn't called from the source side code of
guest migration.
Right, but since you are accessing the list from both migration and
non-migration threads, qemu_get_ram_ptr needs to take the ram_list lock.
The ram_list and IO thread mutexes together protect the "next" member,
and you need to hold them both when modifying the list.
See the reply to Marcelo for a proposed solution.
Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
