From: Avi Kivity <avi@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration
Date: Tue, 15 Nov 2011 15:04:11 +0200 [thread overview]
Message-ID: <4EC2634B.7010604@redhat.com> (raw)
In-Reply-To: <20111115083257.GA24446@stefanha-thinkpad.localdomain>
On 11/15/2011 10:32 AM, Stefan Hajnoczi wrote:
> It would help to have a migration wiki page or document that explains
> the implications of migration on QEMU code - what to look out for in
> device emulation code.
>
> Although regular QEMU contributors may know the background on
> migration/save/load, it would be not only helpful for new contributors
> but also a good refresher for those of us who have picked up the
> assumptions around migration piecewise.
>
> I think a good document would raise migration awareness and help us
> review new patches with an eye towards correct migration behavior.
>
> The rules need to be laid down by someone who understands migration
> quite well.
>
Good idea. There needs to be a good explanation of what the migration
state is; I think that's the biggest obstacle.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-11-15 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-12 16:07 [Qemu-devel] [PATCH] migration: add a MAINTAINERS entry for migration Anthony Liguori
2011-11-14 17:40 ` Juan Quintela
2011-11-14 21:08 ` Anthony Liguori
2011-11-15 8:32 ` Stefan Hajnoczi
2011-11-15 13:04 ` Avi Kivity [this message]
2011-11-15 13:45 ` Anthony Liguori
2011-11-15 9:36 ` Kevin Wolf
2011-11-15 13:50 ` Anthony Liguori
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=4EC2634B.7010604@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@gmail.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).