From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] vm state save/restore question
Date: Wed, 20 Jun 2012 07:13:41 +1000 [thread overview]
Message-ID: <1340140421.28143.39.camel@pasglop> (raw)
In-Reply-To: <C8F69AD1-955B-4E27-99FB-D3E494D71898@suse.de>
On Tue, 2012-06-19 at 23:00 +0200, Alexander Graf wrote:
> How is the problem different from RAM? It's a 16MB region that can be
> accessed by the guest even during transfer time, so it can get dirty
> during the migration. But we only need to really transfer the last
> small delta at the end of the migration, right?
Because with -M pseries it's not mapped into guest space but instead is
a chunk of physically contiguous memory accessed directly in real mode
by KVM. So no dirty tracking here.
We could keep track manually maybe using some kind of dirty bitmap of
changes to the hash table but that would add overhead to things like
H_ENTER.
Cheers,
Ben.
next prev parent reply other threads:[~2012-06-19 21:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-09 10:53 [Qemu-devel] vm state save/restore question Benjamin Herrenschmidt
2012-06-09 11:34 ` Benjamin Herrenschmidt
2012-06-09 11:37 ` Andreas Färber
2012-06-19 14:07 ` Alexander Graf
2012-06-19 14:59 ` Juan Quintela
2012-06-19 17:16 ` Andreas Färber
2012-06-19 20:30 ` Benjamin Herrenschmidt
2012-06-19 21:00 ` Alexander Graf
2012-06-19 21:13 ` Benjamin Herrenschmidt [this message]
2012-06-19 21:48 ` Alexander Graf
2012-06-19 21:51 ` Benjamin Herrenschmidt
2012-06-19 22:27 ` Alexander Graf
2012-06-19 22:32 ` Benjamin Herrenschmidt
2012-06-19 22:55 ` Juan Quintela
2012-06-19 23:00 ` Benjamin Herrenschmidt
2012-06-19 23:11 ` Juan Quintela
2012-06-19 23:28 ` Benjamin Herrenschmidt
2012-06-19 23:30 ` Alexander Graf
2012-06-19 23:52 ` Benjamin Herrenschmidt
2012-06-20 0:05 ` Alexander Graf
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=1340140421.28143.39.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--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).