From: Isaku Yamahata <yamahata@valinux.co.jp>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: benoit.hudzia@gmail.com, aarcange@redhat.com,
aliguori@us.ibm.com, arnd@arndb.de, quintela@redhat.com,
stefanha@gmail.com, t.hirofuchi@aist.go.jp, dlaor@redhat.com,
satoshi.itoh@aist.go.jp, mdroth@linux.vnet.ibm.com,
yoshikawa.takuya@oss.ntt.co.jp, owasserm@redhat.com,
avi@redhat.com, gregkh@linuxfoundation.org, pbonzini@redhat.com,
chegu_vinod@hp.com
Subject: [Qemu-devel] [PATCH v4 0/2] postcopy migration: uvmem: Linux char device for postcopy
Date: Tue, 30 Oct 2012 17:34:34 +0900 [thread overview]
Message-ID: <cover.1351584881.git.yamahata@valinux.co.jp> (raw)
This is Linux kernel driver for qemu/kvm postcopy live migration.
This is used by qemu/kvm postcopy live migration patch.
User process backed memory driver provides /dev/uvmem device.
This /dev/uvmem device is designed for some sort of distributed shared memory.
page fault in the area backed by this driver is propagated to (other) server
process which serves the page contents. Usually the server process fetches
page contents from the remote machine. Then the faulting process continues.
ioctl UVMEM_INIT: initialize uvmem device for qemu.
Returns file descriptor of tmpfs, serving thread write
page contents to this file descriptor.
mmap: Guest VM mmaps this device and use it as guest RAM. page fault on
this area will be propagated to the service process.
read: returns page offset that guest VM page-faulted.
write: server process notifies the device which pages are served, then
guest VM can resume execution.
---
Changes v3 -> v4:
- rename module name: umem -> uvmem
avoid module name conflict
Changes v2 -> v3:
- make fault handler killable
- make use of read()/write()
- documentation
Changes version 1 -> 2:
- make ioctl structures padded to align
- un-KVM
KVM_VMEM -> UMEM
- dropped some ioctl commands as Avi requested
Isaku Yamahata (2):
export necessary symbols
umem: chardevice for kvm postcopy
Documentation/misc-devices/uvmem.txt | 292 ++++++++++++
drivers/char/Kconfig | 10 +
drivers/char/Makefile | 1 +
drivers/char/uvmem.c | 841 ++++++++++++++++++++++++++++++++++
include/linux/uvmem.h | 41 ++
mm/memcontrol.c | 1 +
mm/mempolicy.c | 1 +
mm/shmem.c | 1 +
8 files changed, 1188 insertions(+)
create mode 100644 Documentation/misc-devices/uvmem.txt
create mode 100644 drivers/char/uvmem.c
create mode 100644 include/linux/uvmem.h
--
1.7.10.4
next reply other threads:[~2012-10-30 8:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 8:34 Isaku Yamahata [this message]
2012-10-30 8:34 ` [Qemu-devel] [PATCH v4 1/2] export necessary symbols Isaku Yamahata
2012-10-30 8:34 ` [Qemu-devel] [PATCH v4 2/2] umem: chardevice for kvm postcopy Isaku Yamahata
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=cover.1351584881.git.yamahata@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=aarcange@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=benoit.hudzia@gmail.com \
--cc=chegu_vinod@hp.com \
--cc=dlaor@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdroth@linux.vnet.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=satoshi.itoh@aist.go.jp \
--cc=stefanha@gmail.com \
--cc=t.hirofuchi@aist.go.jp \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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).