From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Cc: Andrew Morton <akpm-3NddpPZAyC0@public.gmane.org>,
linux-kernel
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: [PATCH 0/4] KVM: Dirty page logging (aka live migration) fixes
Date: Sun, 25 Feb 2007 14:54:22 +0200 [thread overview]
Message-ID: <45E186FE.2000909@qumranet.com> (raw)
This small patchset plugs a few holes in the kvm dirty page logging
implementation. With these fixes (which really want to be in Linux
2.6.21), one can migrate a running virtual machine from one host to
another. The virtual machine continues executing while its memory image
is transferred, so there is only a minimal pause in service.
The patchset is also available as part of the kvm git tree; see
http://kvm.qumranet.com/kvmwiki/Code.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2007-02-25 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 12:54 Avi Kivity [this message]
[not found] ` <45E186FE.2000909-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-02-25 12:55 ` [PATCH 1/4] KVM: Add missing calls to mark_page_dirty() Avi Kivity
2007-02-25 12:56 ` [PATCH 2/4] KVM: Fix dirty page log bitmap size/access calculation Avi Kivity
2007-02-25 12:57 ` [PATCH 3/4] kvm: move do_remove_write_access() up Avi Kivity
2007-02-25 12:58 ` [PATCH 4/4] KVM: Remove write access permissions when dirty-page-logging is enabled Avi Kivity
2007-02-25 13:11 ` [PATCH 0/4] KVM: Dirty page logging (aka live migration) fixes Avi Kivity
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=45E186FE.2000909@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=akpm-3NddpPZAyC0@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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