From: David Gibson <david@gibson.dropbear.id.au>
To: aliguori@us.ibm.com, quintela@redhat.com
Cc: aik@ozlabs.ru, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: [Qemu-devel] [0/2] Migration bugfixes that were forgotten for 1.3
Date: Tue, 4 Dec 2012 11:38:37 +1100 [thread overview]
Message-ID: <1354581520-25993-1-git-send-email-david@gibson.dropbear.id.au> (raw)
I've sent these before, and reminded several times about the first one
at least, but they still slipped through the cracks and didn't make it
into 1.3. The first at least should go into the stable tree - it is a
very simple bugfix for a serious bug (qemu and possibly also guest
memory corruption).
next reply other threads:[~2012-12-04 0:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 0:38 David Gibson [this message]
2012-12-04 0:38 ` [Qemu-devel] [PATCH 1/2] Fix off-by-1 error in RAM migration code David Gibson
2012-12-04 0:38 ` [Qemu-devel] [PATCH 2/2] migration: Fix madvise breakage if host and guest have different page sizes David Gibson
2012-12-04 0:55 ` [Qemu-devel] [0/2] Migration bugfixes that were forgotten for 1.3 Anthony Liguori
2012-12-04 11:44 ` Juan Quintela
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=1354581520-25993-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).