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" <quintela@redhat.com>
Subject: Re: [Qemu-devel] vm state save/restore question
Date: Wed, 20 Jun 2012 07:51:55 +1000 [thread overview]
Message-ID: <1340142715.28143.41.camel@pasglop> (raw)
In-Reply-To: <99D704E3-384D-42C6-997C-379D850AC347@suse.de>
On Tue, 2012-06-19 at 23:48 +0200, Alexander Graf wrote:
> > 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.
>
> Only during migration, right?
True. It will be an "interesting" user/kernel API tho ... I'll give it more thoughts.
I need to understand better how do that vs. qemu save/restore though. IE. That means
we can't just save the hash as a bulk and reload it, but we'd have to save bits of
it at a time or something like that no ? Or do we save it once, then save the diff
at the end ?
Cheers,
Ben.
next prev parent reply other threads:[~2012-06-19 21:52 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
2012-06-19 21:48 ` Alexander Graf
2012-06-19 21:51 ` Benjamin Herrenschmidt [this message]
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=1340142715.28143.41.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 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.