From: Pavel Fedin <p.fedin@samsung.com>
To: "'Dr. David Alan Gilbert'" <dgilbert@redhat.com>
Cc: 'QEMU' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Live migration sequence
Date: Tue, 13 Oct 2015 13:06:33 +0300 [thread overview]
Message-ID: <00b801d1059e$d6d4ffb0$847eff10$@samsung.com> (raw)
In-Reply-To: <20151009152942.GF2702@work-vm>
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
next prev parent reply other threads:[~2015-10-13 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 11:39 [Qemu-devel] Live migration sequence Pavel Fedin
2015-10-09 15:29 ` Dr. David Alan Gilbert
2015-10-13 10:06 ` Pavel Fedin [this message]
2015-10-13 11:05 ` Dr. David Alan Gilbert
2015-10-13 12:02 ` Pavel Fedin
2015-10-13 12:04 ` Peter Maydell
2015-10-13 12:41 ` Pavel Fedin
2015-10-16 7:24 ` Pavel Fedin
2015-10-16 17:11 ` Dr. David Alan Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='00b801d1059e$d6d4ffb0$847eff10$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).