qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cam Macdonell <cam@cs.ualberta.ca>
To: qemu-devel@nongnu.org
Cc: Cam Macdonell <cam@cs.ualberta.ca>, kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH v8 0/5] Inter-VM Shared Memory Device
Date: Mon, 26 Jul 2010 18:10:56 -0600	[thread overview]
Message-ID: <1280189461-1929-1-git-send-email-cam@cs.ualberta.ca> (raw)

Latest patch for PCI shared memory device that maps a host shared memory object
to be shared between guests

new in this series

    v8
    - rebased to qemu.git
    - added qemu_ram_alloc_from_ptr() function
    - removed irqfd support as support functions are not yet in qemu

    v7
    - replace marking memory from v6 with marking device as unmigratable indicating
      that it should be unplugged before migration and re-added after.
    - 'peer' case changed to require removal before migration, only 'master'
      devices can be migrated while attached.

    v6
    - migration support with 'master' and 'peer' roles for guest to determine
      who "owns" memory
    - modified phys_ram_dirty array for marking memory as not to be migrated

    v5:
    - fixed segfault for non-server case
    - code style fixes
    - removed limit on the number of guests
    - shared memory server is now in qemu.git/contrib
    - made ioeventfd setup function generic
    - removed interrupts when guest joined (let application handle it)

    v4:
    - moved to single Doorbell register and use datamatch to trigger different
      VMs rather than one register per eventfd
    - remove writing arbitrary values to eventfds.  Only values of 1 are now
      written to ensure correct usage

Cam Macdonell (5):
  Provide a function to add an allocated region of memory to the qemu
    RAM.
  Device specification for shared memory PCI device
  Add function to assign ioeventfd to MMIO.
  Support marking a device as non-migratable
  Inter-VM shared memory PCI device

 Makefile.target                    |    3 +
 cpu-common.h                       |    2 +
 docs/specs/ivshmem_device_spec.txt |   96 ++++
 exec.c                             |   43 ++
 hw/hw.h                            |    2 +
 hw/ivshmem.c                       |  834 ++++++++++++++++++++++++++++++++++++
 kvm-all.c                          |   32 ++
 kvm.h                              |    1 +
 qemu-char.c                        |    6 +
 qemu-char.h                        |    3 +
 qemu-doc.texi                      |   43 ++
 savevm.c                           |   44 ++-
 12 files changed, 1106 insertions(+), 3 deletions(-)
 create mode 100644 docs/specs/ivshmem_device_spec.txt
 create mode 100644 hw/ivshmem.c

             reply	other threads:[~2010-07-27  0:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27  0:10 Cam Macdonell [this message]
2010-07-27  0:10 ` [Qemu-devel] [PATCH v8 1/5] Add qemu_ram_alloc_from_ptr function Cam Macdonell
2010-07-27  0:10   ` [Qemu-devel] [PATCH v8 2/5] Device specification for shared memory PCI device Cam Macdonell
2010-07-27  0:10     ` [Qemu-devel] [PATCH v8 3/5] Add function to assign ioeventfd to MMIO Cam Macdonell
2010-07-27  0:11       ` [Qemu-devel] [PATCH v8 4/5] Support marking a device as non-migratable Cam Macdonell
2010-07-27  0:11         ` [Qemu-devel] [PATCH v8 5/5] Inter-VM shared memory PCI device Cam Macdonell
2010-07-27 16:54           ` [Qemu-devel] [PATCH v8 5/5] RESEND: " Cam Macdonell
2010-08-11  8:35             ` Stefan Weil
2010-08-11 15:49               ` Cam Macdonell
2010-08-11 17:07                 ` Paolo Bonzini
2010-08-11 18:22                   ` Stefan Weil
2010-08-10 21:28   ` [Qemu-devel] [PATCH v8 1/5] Add qemu_ram_alloc_from_ptr function Anthony Liguori

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=1280189461-1929-1-git-send-email-cam@cs.ualberta.ca \
    --to=cam@cs.ualberta.ca \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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).