xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Oleksandr Andrushchenko <andr2000@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>, xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com, julien.grall@arm.com,
	ian.jackson@eu.citrix.com, blackskygg@gmail.com
Subject: Re: [PATCH v5 0/6] Allow setting up shared memory areas between VMs from xl config files
Date: Wed, 24 Oct 2018 17:15:55 +0300	[thread overview]
Message-ID: <192e0efc-417e-a26d-6373-7a775fec3f22@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1805241750440.25719@sstabellini-ThinkPad-X260>

Hi, Stefano!

I'm just curious if the below is on your TODO list [1]:

3. Future Directions:
====================================================

Allow users to optionally share *mfn-contiguous* pages.

Thank you,
Oleksandr

On 05/25/2018 03:55 AM, Stefano Stabellini wrote:
> Hi,
>
> 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. I
> tested the feature on ARM and works fine.
>
> Cheers,
>
> Stefano
>
>
> 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 | 257 +++++++++++++++
>   docs/man/xl.cfg.pod.5.in                   |   8 +
>   docs/misc/xenstore-paths.markdown          |  47 +++
>   tools/flask/policy/modules/xen.if          |   2 +
>   tools/libxl/Makefile                       |   4 +-
>   tools/libxl/libxl.h                        |   6 +
>   tools/libxl/libxl_arch.h                   |   6 +
>   tools/libxl/libxl_arm.c                    |  15 +
>   tools/libxl/libxl_create.c                 |  27 ++
>   tools/libxl/libxl_domain.c                 |   5 +
>   tools/libxl/libxl_internal.h               |  16 +
>   tools/libxl/libxl_sshm.c                   | 512 +++++++++++++++++++++++++++++
>   tools/libxl/libxl_types.idl                |  32 +-
>   tools/libxl/libxl_x86.c                    |  19 ++
>   tools/libxl/libxlu_sshm.c                  | 207 ++++++++++++
>   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                    |  15 +
>   xen/include/xsm/xsm.h                      |   6 +
>   xen/xsm/dummy.c                            |   1 +
>   xen/xsm/flask/hooks.c                      |  12 +
>   xen/xsm/flask/policy/access_vectors        |   5 +
>   24 files changed, 1242 insertions(+), 6 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
[1] https://lists.xen.org/archives/html/xen-devel/2017-08/msg03242.html

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

  parent reply	other threads:[~2018-10-24 14:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25  0:55 [PATCH v5 0/6] Allow setting up shared memory areas between VMs from xl config files Stefano Stabellini
2018-05-25  0:55 ` [PATCH v5 1/6] xen: xsm: flask: introduce XENMAPSPACE_gmfn_share for memory sharing Stefano Stabellini
2018-05-25  0:55 ` [PATCH v5 2/6] libxl: introduce a new structure to represent static shared memory regions Stefano Stabellini
2018-05-25  0:55 ` [PATCH v5 3/6] libxl: support mapping static shared memory areas during domain creation Stefano Stabellini
2018-05-25  0:55 ` [PATCH v5 4/6] libxl: support unmapping static shared memory areas during domain destruction Stefano Stabellini
2018-05-25  0:55 ` [PATCH v5 5/6] libxl:xl: add parsing code to parse "libxl_static_sshm" from xl config files Stefano Stabellini
2018-05-25  0:55 ` [PATCH v5 6/6] docs: documentation about static shared memory regions Stefano Stabellini
2018-05-26  0:50 ` [PATCH v5 0/6] Allow setting up shared memory areas between VMs from xl config files Zhongze Liu
2018-05-29 21:24   ` Stefano Stabellini
2018-10-24 14:15 ` Oleksandr Andrushchenko [this message]
2018-10-24 14:24   ` Julien Grall
2018-10-24 14:32     ` Oleksandr Andrushchenko
2018-10-24 14:33       ` Julien Grall

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=192e0efc-417e-a26d-6373-7a775fec3f22@gmail.com \
    --to=andr2000@gmail.com \
    --cc=blackskygg@gmail.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --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).