xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: xen-devel@lists.xen.org
Cc: ian.jackson@eu.citrix.com, julien.grall@arm.com,
	sstabellini@kernel.org, wei.liu2@citrix.com,
	blackskygg@gmail.com
Subject: [PATCH v9 0/7] Allow setting up shared memory areas between VMs from xl config files
Date: Wed, 5 Dec 2018 14:15:46 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1812051413450.527@sstabellini-ThinkPad-X260> (raw)

Hi all,

This series implements a new xl config entry. Users can use the new
config entry to statically setup shared memory areas among VMs that
don't have grant table support so that they could communicate with each
other through the static shared memory areas.

It was originally developed by Zhongze, I am just updating the last few
issued that were address during the last round of reviews in January.

Cheers,

Stefano



The following changes since commit 85b00385827e4e061b2ff38b549c03d0f1e66b6a:

  xen/sched: Drop set_current_state() (2018-10-08 18:34:55 +0100)

are available in the git repository at:

  http://xenbits.xenproject.org/git-http/people/sstabellini/xen-unstable.git share_mem-v9

for you to fetch changes up to a900b724d91a1147170f14f340cc231e519eea79:

  xen/arm: export shared memory regions as reserved-memory on device tree (2018-12-05 13:25:02 -0800)

----------------------------------------------------------------
Stefano Stabellini (1):
      xen/arm: export shared memory regions as reserved-memory on device tree

Zhongze Liu (6):
      xen: xsm: flask: introduce XENMAPSPACE_gmfn_share for memory sharing
      libxl: introduce a new structure to represent static shared memory regions
      libxl: support mapping static shared memory areas during domain creation
      libxl: support unmapping static shared memory areas during domain destruction
      libxl:xl: add parsing code to parse "libxl_static_sshm" from xl config files
      docs: documentation about static shared memory regions

 docs/man/xl-static-shm-configuration.pod.5 | 266 +++++++++++++++
 docs/man/xl.cfg.pod.5.in                   |   8 +
 docs/misc/xenstore-paths.markdown          |  47 +++
 tools/flask/policy/modules/xen.if          |   2 +
 tools/libxl/Makefile                       |   5 +-
 tools/libxl/libxl.h                        |   8 +
 tools/libxl/libxl_arch.h                   |   8 +-
 tools/libxl/libxl_arm.c                    |  81 ++++-
 tools/libxl/libxl_create.c                 |  27 ++
 tools/libxl/libxl_dom.c                    |   2 +-
 tools/libxl/libxl_domain.c                 |   8 +
 tools/libxl/libxl_internal.h               |  16 +
 tools/libxl/libxl_sshm.c                   | 530 +++++++++++++++++++++++++++++
 tools/libxl/libxl_types.idl                |  28 ++
 tools/libxl/libxl_x86.c                    |  21 +-
 tools/libxl/libxlu_sshm.c                  | 206 +++++++++++
 tools/libxl/libxlutil.h                    |   6 +
 tools/xl/xl_parse.c                        |  25 +-
 xen/arch/arm/mm.c                          |   7 +-
 xen/include/public/memory.h                |   8 +
 xen/include/xsm/dummy.h                    |  14 +
 xen/include/xsm/xsm.h                      |   6 +
 xen/xsm/dummy.c                            |   1 +
 xen/xsm/flask/hooks.c                      |   7 +
 xen/xsm/flask/policy/access_vectors        |   5 +
 25 files changed, 1332 insertions(+), 10 deletions(-)
 create mode 100644 docs/man/xl-static-shm-configuration.pod.5
 create mode 100644 tools/libxl/libxl_sshm.c
 create mode 100644 tools/libxl/libxlu_sshm.c

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2018-12-05 22:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05 22:15 Stefano Stabellini [this message]
2018-12-05 22:15 ` [PATCH v9 1/7] xen: xsm: flask: introduce XENMAPSPACE_gmfn_share for memory sharing Stefano Stabellini
2018-12-07 19:33   ` Daniel De Graaf
2018-12-05 22:15 ` [PATCH v9 2/7] libxl: introduce a new structure to represent static shared memory regions Stefano Stabellini
2018-12-05 22:15 ` [PATCH v9 3/7] libxl: support mapping static shared memory areas during domain creation Stefano Stabellini
2018-12-05 22:16 ` [PATCH v9 4/7] libxl: support unmapping static shared memory areas during domain destruction Stefano Stabellini
2018-12-05 22:16 ` [PATCH v9 5/7] libxl:xl: add parsing code to parse "libxl_static_sshm" from xl config files Stefano Stabellini
2018-12-05 22:16 ` [PATCH v9 6/7] docs: documentation about static shared memory regions Stefano Stabellini
2018-12-05 22:16 ` [PATCH v9 7/7] xen/arm: export shared memory regions as reserved-memory on device tree Stefano Stabellini
2018-12-07 21:06   ` Stefano Stabellini
  -- strict thread matches above, loose matches on Subject: below --
2018-12-05 21:19 [PATCH v9 0/7] Allow setting up shared memory areas between VMs from xl config files Stefano Stabellini
2018-12-05 21:27 ` Stefano Stabellini

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=alpine.DEB.2.10.1812051413450.527@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=blackskygg@gmail.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@arm.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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).