From: Isaku Yamahata <yamahata@valinux.co.jp>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Cc: yamahata@valinux.co.jp, t.hirofuchi@aist.go.jp, satoshi.itoh@aist.go.jp
Subject: [Qemu-devel] [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy
Date: Thu, 29 Dec 2011 10:26:16 +0900 [thread overview]
Message-ID: <cover.1325055065.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.
TODO:
- Consider FUSE/CUSE option
So far several mmap patches for FUSE/CUSE are floating around. (their
purpose isn't different from our purpose, though). They haven't merged
into the upstream yet.
The driver specific part in qemu patches is modularized. So I expect it
wouldn't be difficult to switch kernel driver to CUSE based driver.
ioctl commands:
UMEM_DEV_CRATE_UMEM: create umem device for qemu
UMEM_DEV_LIST: list created umem devices
UMEM_DEV_REATTACH: re-attach the created umem device
UMEM_DEV_LIST and UMEM_DEV_REATTACH are used when
the process that services page fault disappears or get stack.
Then, administrator can list the umem devices and unblock
the process which is waiting for page.
UMEM_GET_PAGE_REQUEST: retrieve page fault of qemu process
UMEM_MARK_PAGE_CACHED: mark the specified pages pulled from the source
for daemon
UMEM_MAKE_VMA_ANONYMOUS: make the specified vma in the qemu process
This is _NOT_ implemented yet.
anonymous I'm not sure whether this can be implemented
or not.
---
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
drivers/char/Kconfig | 9 +
drivers/char/Makefile | 1 +
drivers/char/umem.c | 898 +++++++++++++++++++++++++++++++++++++++++++++++++
include/linux/umem.h | 83 +++++
mm/memcontrol.c | 1 +
mm/shmem.c | 1 +
6 files changed, 993 insertions(+), 0 deletions(-)
create mode 100644 drivers/char/umem.c
create mode 100644 include/linux/umem.h
next reply other threads:[~2011-12-29 1:26 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 1:26 Isaku Yamahata [this message]
2011-12-29 1:26 ` [Qemu-devel] [PATCH 1/2] export necessary symbols Isaku Yamahata
2011-12-29 1:26 ` [Qemu-devel] [PATCH 2/2] umem: chardevice for kvm postcopy Isaku Yamahata
2011-12-29 11:17 ` Avi Kivity
2011-12-29 12:22 ` Isaku Yamahata
2011-12-29 12:47 ` Avi Kivity
2012-01-05 4:08 ` [Qemu-devel] 回复: " thfbjyddx
2012-01-05 10:48 ` [Qemu-devel] 回??: " Isaku Yamahata
2012-01-05 11:10 ` Tommy
2012-01-05 12:18 ` Isaku Yamahata
2012-01-05 15:02 ` Tommy Tang
[not found] ` <4F05BB68.9050302@hotmail.com>
2012-01-05 15:05 ` Tommy Tang
2012-01-06 7:02 ` thfbjyddx
2012-01-06 17:13 ` [Qemu-devel] 回??: [PATCH 2/2] umem: chardevice for kvm?postcopy Isaku Yamahata
2011-12-29 1:31 ` [Qemu-devel] [PATCH 0/2][RFC] postcopy migration: Linux char device for postcopy Isaku Yamahata
2011-12-29 11:24 ` Avi Kivity
2011-12-29 12:39 ` Isaku Yamahata
2011-12-29 12:55 ` Avi Kivity
2011-12-29 13:49 ` Isaku Yamahata
2011-12-29 13:52 ` Avi Kivity
2011-12-29 14:18 ` Isaku Yamahata
2011-12-29 14:35 ` Avi Kivity
2011-12-29 14:49 ` Isaku Yamahata
2011-12-29 14:55 ` Avi Kivity
2011-12-29 15:53 ` Isaku Yamahata
2011-12-29 16:00 ` Avi Kivity
2011-12-29 16:01 ` Avi Kivity
2012-01-02 17:05 ` Andrea Arcangeli
2012-01-02 17:55 ` Paolo Bonzini
2012-01-03 14:25 ` Andrea Arcangeli
2012-01-12 13:57 ` Avi Kivity
2012-01-13 2:06 ` Andrea Arcangeli
2012-01-04 3:03 ` Isaku Yamahata
2012-01-12 13:59 ` Avi Kivity
2012-01-13 1:09 ` Benoit Hudzia
2012-01-13 1:31 ` Takuya Yoshikawa
2012-01-13 9:40 ` Benoit Hudzia
2012-01-13 2:03 ` Isaku Yamahata
2012-01-13 2:15 ` Isaku Yamahata
2012-01-13 9:55 ` Benoit Hudzia
2012-01-13 9:48 ` Benoit Hudzia
2012-01-13 2:09 ` Andrea Arcangeli
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.1325055065.git.yamahata@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=satoshi.itoh@aist.go.jp \
--cc=t.hirofuchi@aist.go.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).