[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Live migration sequence
From: |
Pavel Fedin |
Subject: |
Re: [Qemu-devel] Live migration sequence |
Date: |
Tue, 13 Oct 2015 13:06:33 +0300 |
Hello!
Sorry for the delayed reply.
> What's an ITS ?
Interrupt Translation Service. In a short, it's a thing responsible for
handling PCIe MSI-X
interrupts on ARM64 architecture.
> With a related question, how big are the tables and can it change during the
> iterated part
> of the migrate?
Tables are something like 64K each. They hold mappings between device/event
IDs and actual IRQ
numbers.
Unfortunately i don't know how to answer the second part of the question,
about iterated part. Can
you explain in details, what is it and how does it work?
Or, well, we could put the question the other way: imagine that in pre_save i
tell my emulated
device to flush its cached state into RAM-based tables. In post_load i could
tell the device to
re-read data from RAM into its cache. So, what do i need in order to make these
tables in RAM to
migrate correctly?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia