From: Glauber Costa <glommer@redhat.com>
To: kvm@vger.kernel.org
Cc: avi@redhat.com
Subject: [PATCH 0/3] Fix migration of linux guests using kvmclock
Date: Fri, 16 Oct 2009 15:27:36 -0400 [thread overview]
Message-ID: <1255721259-11740-1-git-send-email-glommer@redhat.com> (raw)
This series uses the new ioctl I've just posted to the kernel.
It is pretty straightforward usage.
We first have to save and restore kvm msr registers, and later, which
is done in patch 2. It has nothing to do with our ioctls, but is required
for the whole thing to work.
Patch 1 is a dependency, that quintela plans on sending to qemu.git too,
but is provided here for people that might want to test it.
next reply other threads:[~2009-10-16 19:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 19:27 Glauber Costa [this message]
2009-10-16 19:27 ` [PATCH 1/3] introduce VMSTATE_U64 Glauber Costa
2009-10-16 19:27 ` [PATCH 2/3] properly save kvm system time msr registers Glauber Costa
2009-10-16 19:27 ` [PATCH 3/3] get and set clock upon migration Glauber Costa
2009-10-19 23:40 ` [PATCH 1/3] introduce VMSTATE_U64 Avi Kivity
2009-10-20 0:38 ` Glauber Costa
2009-10-19 19:51 ` [PATCH 0/3] Fix migration of linux guests using kvmclock Marcelo Tosatti
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=1255721259-11740-1-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.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