From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL for-2.1 0/2] Two fixes for KVM and memory
Date: Tue, 22 Jul 2014 12:51:08 +0200 [thread overview]
Message-ID: <1406026270-17238-1-git-send-email-pbonzini@redhat.com> (raw)
The following changes since commit fa666c10f2f3e15685ff88abd3bc433ddce012d6:
Revert "kvmclock: Ensure time in migration never goes backward" (2014-07-18 15:28:03 +0200)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-upstream
for you to fetch changes up to dc54e2525389e903cee2b847cf761b5d857f75cb:
kvm-all: Use 'tmpcpu' instead of 'cpu' in sub-looping to avoid 'cpu' be NULL (2014-07-22 12:38:17 +0200)
----------------------------------------------------------------
One of the two pending migration fix, and a small KVM patch.
----------------------------------------------------------------
Chen Gang (1):
kvm-all: Use 'tmpcpu' instead of 'cpu' in sub-looping to avoid 'cpu' be NULL
Paolo Bonzini (1):
exec: fix migration with devices that use address_space_rw
exec.c | 20 ++++----------------
include/exec/ram_addr.h | 11 +++++++++++
kvm-all.c | 5 +++--
3 files changed, 18 insertions(+), 18 deletions(-)
--
1.8.3.1
next reply other threads:[~2014-07-22 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 10:51 Paolo Bonzini [this message]
2014-07-22 10:51 ` [Qemu-devel] [PULL 1/2] exec: fix migration with devices that use address_space_rw Paolo Bonzini
2014-07-22 10:51 ` [Qemu-devel] [PULL 2/2] kvm-all: Use 'tmpcpu' instead of 'cpu' in sub-looping to avoid 'cpu' be NULL Paolo Bonzini
2014-07-22 12:14 ` [Qemu-devel] [PULL for-2.1 0/2] Two fixes for KVM and memory Peter Maydell
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=1406026270-17238-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).