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, 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, pbonzini@redhat.com
Subject: [Qemu-devel] [PATCH v3 0/2] postcopy migration: umem: Linux char device for postcopy
Date: Mon, 4 Jun 2012 18:58:38 +0900 [thread overview]
Message-ID: <cover.1338803423.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_INIT: initialize umem device for qemu
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 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/umem.txt | 303 ++++++++++++
drivers/char/Kconfig | 10 +
drivers/char/Makefile | 1 +
drivers/char/umem.c | 900 +++++++++++++++++++++++++++++++++++
include/linux/umem.h | 42 ++
mm/memcontrol.c | 1 +
mm/mempolicy.c | 1 +
mm/shmem.c | 1 +
8 files changed, 1259 insertions(+), 0 deletions(-)
create mode 100644 Documentation/misc-devices/umem.txt
create mode 100644 drivers/char/umem.c
create mode 100644 include/linux/umem.h
next reply other threads:[~2012-06-04 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 9:58 Isaku Yamahata [this message]
2012-06-04 9:58 ` [Qemu-devel] [PATCH v3 1/2] export necessary symbols Isaku Yamahata
2012-06-04 9:58 ` [Qemu-devel] [PATCH v3 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.1338803423.git.yamahata@valinux.co.jp \
--to=yamahata@valinux.co.jp \
--cc=aarcange@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=benoit.hudzia@gmail.com \
--cc=dlaor@redhat.com \
--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).