From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'Juan Quintela' <quintela@redhat.com>,
'Marc Zyngier' <marc.zyngier@arm.com>,
'QEMU' <qemu-devel@nongnu.org>,
"'Dr. David Alan Gilbert'" <dgilbert@redhat.com>,
'Amit Shah' <amit.shah@redhat.com>,
kvmarm@lists.cs.columbia.edu,
'Christoffer Dall' <christoffer.dall@linaro.org>
Subject: Re: [Qemu-devel] Live migration sequence
Date: Tue, 13 Oct 2015 15:41:42 +0300 [thread overview]
Message-ID: <00e001d105b4$83c62c70$8b528550$@samsung.com> (raw)
In-Reply-To: <CAFEAcA8P9okmf012ocoo6bx5y-0yObTFrsrPo1tQ99yGiHYo7A@mail.gmail.com>
Hello!
> Our idea at the discussion at Connect was to have an ioctl to request
> a flush, rather than to do it automatically when a CPU is stopped
> (you probably don't want to flush when only one CPU in an SMP system
> is stopped, for instance).
Yes, you're right. Looks like this would be more complicated but better way to do the thing. I'll look at migration state notifier mechanism.
> But we wanted to get the basic no-ITS ABI sorted out and agreed first
Yes, this is good idea, too much changes otherwise. But here at Samsung we have a project, and it has deadlines, so please understand that i try to do things quickly.
Of course, you see that as soon as i make something, i post it at least as RFCs, because i don't want to have something misdesigned, which will be dropped afterwards. Cooperation with OSS is one of goals of our project.
Thank you very much for your cooperation and explanations.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-13 12:41 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
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 [this message]
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='00e001d105b4$83c62c70$8b528550$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=amit.shah@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=dgilbert@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--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).