From: Marc Zyngier <marc.zyngier@arm.com>
To: ib10evp0@gmx.org
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: Status of live migration on ARMv7
Date: Tue, 14 Jun 2016 22:09:40 +0100 [thread overview]
Message-ID: <20160614220940.171387d5@arm.com> (raw)
In-Reply-To: <trinity-6f860951-3365-4cc6-986a-3b19853fd387-1465937561349@3capp-gmx-bs24>
On Tue, 14 Jun 2016 22:52:41 +0200
<ib10evp0@gmx.org> wrote:
> Hi Marc,
>
> > Everything that's needed for a typical ARMv7 is already in mainline,
> > both for the kernel and qemu. And since the code is almost entirely
> > shared with ARMv8, it is probably in the same state. If it not working,
> > then it is a bug that should be addressed.
> >
> > > BTW: The Migration page [3] claims the migration feature is hardware
> > > independent but it remains unclear if this expands to CPU
> > > architectures and if this applies to live migration or only offline
> > > migration. Some clarification in this regard would be nice to have.
> >
> > We do have support for live migration (migrating the VM whilst it is
> > still running, tracking memory that gets dirtied).
>
> After reading this it's still not entirely clear to me if live migration using
> your definition is also available for ARMv7 in the mainline kernel. Could you
> confirm this with one sentence, please? Sorry for the inconvenience.
I know it is available because I did review the code. Look for commits
7276030 KVM: arm/arm64: Enable Dirty Page logging for ARMv8
15a49a4 KVM: arm: page logging 2nd stage fault handling
53c810c KVM: arm: dirty logging write protect support
c647355 KVM: arm: Add initial dirty page locking support
as well as the generic infrastructure that precede them.
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2016-06-14 21:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 12:40 Status of live migration on ARMv7 ib10evp0
2016-06-14 19:20 ` Marc Zyngier
2016-06-14 20:52 ` ib10evp0
2016-06-14 21:09 ` Marc Zyngier [this message]
2016-06-15 7:57 ` ib10evp0
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=20160614220940.171387d5@arm.com \
--to=marc.zyngier@arm.com \
--cc=ib10evp0@gmx.org \
--cc=kvmarm@lists.cs.columbia.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.