qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Liu Ping Fan <qemulist@gmail.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/6] proposal to make hostmem listener RAM unplug safe
Date: Fri,  3 May 2013 10:45:16 +0800	[thread overview]
Message-ID: <1367549122-2948-1-git-send-email-qemulist@gmail.com> (raw)

v1->v2:
  1.split RCU prepared style update and monitor the RAM-Device refcnt into two patches (patch 2,4)
  2.introduce AddrSpaceMem, which is similar to HostMem, but based on address space, while
    the original HostMem only server system memory address space

Liu Ping Fan (6):
  hostmem: make hostmem single, not per Vring related
  hostmem: AddressSpace has its own map and maintained by RCU prepared
    style
  memory: add ref/unref interface for MemroyRegionOps
  hostmem: hostmem listener pin RAM-Device by refcnt
  Vring: use hostmem's RAM safe api
  virtio-blk: release reference to RAM's memoryRegion

 exec.c                                |    1 +
 hw/block/dataplane/virtio-blk.c       |   52 ++++++++---
 hw/virtio/dataplane/hostmem.c         |  168 +++++++++++++++++++++++++--------
 hw/virtio/dataplane/vring.c           |  100 +++++++++++++++-----
 include/exec/memory.h                 |   11 ++
 include/hw/virtio/dataplane/hostmem.h |   25 +++---
 include/hw/virtio/dataplane/vring.h   |    5 +-
 memory.c                              |   18 ++++
 8 files changed, 289 insertions(+), 91 deletions(-)

-- 
1.7.4.4

             reply	other threads:[~2013-05-03  2:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  2:45 Liu Ping Fan [this message]
2013-05-03  2:45 ` [Qemu-devel] [PATCH v2 1/6] hostmem: make hostmem single, not per Vring related Liu Ping Fan
2013-05-03  8:54   ` Stefan Hajnoczi
2013-05-03  2:45 ` [Qemu-devel] [PATCH v2 2/6] hostmem: AddressSpace has its own map and maintained by RCU prepared style Liu Ping Fan
2013-05-03  9:10   ` Stefan Hajnoczi
2013-05-06  1:44     ` liu ping fan
2013-05-03  2:45 ` [Qemu-devel] [PATCH v2 3/6] memory: add ref/unref interface for MemroyRegionOps Liu Ping Fan
2013-05-03  2:45 ` [Qemu-devel] [PATCH v2 4/6] hostmem: hostmem listener pin RAM-Device by refcnt Liu Ping Fan
2013-05-03  9:35   ` Stefan Hajnoczi
2013-05-06  1:45     ` liu ping fan
2013-05-03  2:45 ` [Qemu-devel] [PATCH v2 5/6] Vring: use hostmem's RAM safe api Liu Ping Fan
2013-05-03 10:02   ` Stefan Hajnoczi
2013-05-06  1:45     ` liu ping fan
2013-05-03  2:45 ` [Qemu-devel] [PATCH v2 6/6] virtio-blk: release reference to RAM's memoryRegion Liu Ping Fan
2013-05-03 10:09   ` Stefan Hajnoczi
2013-05-06  2:39     ` liu ping fan
2013-05-04  9:53 ` [Qemu-devel] [PATCH v2 0/6] proposal to make hostmem listener RAM unplug safe Paolo Bonzini
2013-05-06  1:42   ` liu ping fan
2013-05-06  6:17     ` Paolo Bonzini

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=1367549122-2948-1-git-send-email-qemulist@gmail.com \
    --to=qemulist@gmail.com \
    --cc=aliguori@us.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vasilis.liaskovitis@profitbricks.com \
    /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).