From: Pavel Fedin <p.fedin@samsung.com>
To: 'Peter Maydell' <peter.maydell@linaro.org>
Cc: 'QEMU Developers' <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] arm_gic_kvm: Disable live migration if not supported
Date: Fri, 16 Oct 2015 09:40:07 +0300 [thread overview]
Message-ID: <00a501d107dd$7fd8b350$7f8a19f0$@samsung.com> (raw)
In-Reply-To: <CAFEAcA-ndH_duvEL6vEBzVmU8uWqvJoVCzFEtHsvwFAYtnT2rg@mail.gmail.com>
Hello!
> What kernel are you running that doesn't support state save/restore
> in the GICv2 implementation?
I am not running such an old kernel. Just realized that GICv3 will need something similar, and actually GICv2 needs it too.
Actually this idea came to me when i occasionally tried to migrate a machine with an ITS. My ITS was missing unmigratable flag.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-16 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 12:45 [Qemu-devel] [PATCH] arm_gic_kvm: Disable live migration if not supported Pavel Fedin
2015-10-15 16:38 ` Peter Maydell
2015-10-16 6:40 ` Pavel Fedin [this message]
2015-10-16 7:36 ` Peter Maydell
2015-10-16 7:52 ` Pavel Fedin
2015-10-16 13:10 ` Peter Maydell
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='00a501d107dd$7fd8b350$7f8a19f0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=peter.maydell@linaro.org \
--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).