lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 30 Oct 2012 17:34:34 +0900
From:	Isaku Yamahata <yamahata@...inux.co.jp>
To:	qemu-devel@...gnu.org, kvm@...r.kernel.org,
	linux-kernel@...r.kernel.org
Cc:	owasserm@...hat.com, quintela@...hat.com, avi@...hat.com,
	pbonzini@...hat.com, aliguori@...ibm.com, stefanha@...il.com,
	dlaor@...hat.com, mdroth@...ux.vnet.ibm.com,
	yoshikawa.takuya@....ntt.co.jp, benoit.hudzia@...il.com,
	aarcange@...hat.com, t.hirofuchi@...t.go.jp,
	satoshi.itoh@...t.go.jp, chegu_vinod@...com,
	gregkh@...uxfoundation.org, arnd@...db.de
Subject: [PATCH v4 0/2]  postcopy migration: uvmem: Linux char device for postcopy

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ