From: Pavel Fedin <p.fedin@samsung.com>
To: quintela@redhat.com
Cc: 'Amit Shah' <amit.shah@redhat.com>,
qemu-devel@nongnu.org, 'Luiz Capitulino' <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration: Introduce migration_in_completion()
Date: Tue, 27 Oct 2015 17:03:42 +0300 [thread overview]
Message-ID: <002b01d110c0$4a5c8e40$df15aac0$@samsung.com> (raw)
In-Reply-To: <87k2q8e8d4.fsf@neno.neno>
Hello!
> Applied, thanks.
Thank you.
> I wonder who it has never been needed before. BTW, what is ITS?
ITS is Interrupt Translation Service. It is used by ARM64 architecture. In a short, it is a special hardware which performs
table-based lookup of MSI IDs and their destination CPUs, and routes them. There can be lots of CPUs and lots of interrupts, so
these tables are large and are held in a system RAM.
qemu implementation of this thing needs to be able to flush its internal cached state into memory for live migration. This has to
be done during final stage, right after CPUs have been stopped, because right after this point migration code will recheck RAM
status and send out modified data for the last time.
The implementation itself has to wait, because the necessary KVM API is also not ready yet, but i prefer to upstream as much of the
infrastructure as possible, because: a) we want to reduce amount of out-of-tree patches for our project; b) these things affect qemu
core code, and upstreaming them makes sure that we do it right, and our out-of-tree code will not diverge from the upstream too
much.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-27 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 11:01 [Qemu-devel] [PATCH] migration: Introduce migration_in_completion() Pavel Fedin
2015-10-27 13:41 ` Juan Quintela
2015-10-27 14:03 ` Pavel Fedin [this message]
2015-10-28 9:58 ` Juan Quintela
2015-10-28 10:27 ` Pavel Fedin
2015-10-28 11:36 ` Pavel Fedin
2015-10-29 12:20 ` Juan Quintela
2015-10-29 13:36 ` Pavel Fedin
2015-10-29 14:37 ` Juan Quintela
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='002b01d110c0$4a5c8e40$df15aac0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=amit.shah@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).