xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Zhongze Liu <blackskygg@gmail.com>
Cc: Wei Liu <wei.liu2@citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 6/6] libxl: support unmapping static shared memory areas during domain destruction
Date: Fri, 25 Aug 2017 12:05:48 +0100	[thread overview]
Message-ID: <20170825110548.e3ppbaxo4eh4esi6@citrix.com> (raw)
In-Reply-To: <20170822180840.20981-7-blackskygg@gmail.com>

On Wed, Aug 23, 2017 at 02:08:40AM +0800, Zhongze Liu wrote:
> Add libxl__sshm_del to Unmap static shared memory areas mapped by

Unmap -> unmap

> libxl__sshm_add during domain creation. The unmapping process is:
> 
> * For a master: check if it still has living slaves: 1) if yes, mark its
>   status as "zombie", and don't destroy the information under
>   /local/static_shm; 2) if no, simply cleanup related xs entries
> * For a slave: unmap the shared pages, and cleanup related xs entries. If
>   this is the only slave, and it's master is in zombie state, also cleanup
>   the master entries.

I still think refcounting the node is better than this customised
protocol.

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

      parent reply	other threads:[~2017-08-25 11:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 18:08 [PATCH 0/6] Allow setting up shared memory areas between VMs from xl config files Zhongze Liu
2017-08-22 18:08 ` [PATCH 1/6] libxc: add xc_domain_remove_from_physmap to wrap XENMEM_remove_from_physmap Zhongze Liu
2017-08-23 16:14   ` Wei Liu
2017-08-22 18:08 ` [PATCH 2/6] libxl: introduce a new structure to represent static shared memory regions Zhongze Liu
2017-08-22 20:05   ` Stefano Stabellini
2017-08-23  2:05     ` Zhongze Liu
2017-08-22 18:08 ` [PATCH 3/6] libxl:xl: add parsing code to parse "libxl_static_sshm" from xl config files Zhongze Liu
2017-08-22 20:36   ` Stefano Stabellini
2017-08-23 10:58     ` Julien Grall
2017-08-22 18:08 ` [PATCH 4/6] xsm: flask: change the interface and default policy for xsm_map_gmfn_foregin Zhongze Liu
2017-08-22 19:58   ` Stefano Stabellini
2017-08-23  2:18     ` Zhongze Liu
2017-08-23 15:56       ` Daniel De Graaf
2017-08-23  9:55   ` Jan Beulich
2017-08-23 17:16     ` Stefano Stabellini
2017-08-24  6:32       ` Jan Beulich
2017-08-24  0:51     ` Zhongze Liu
2017-08-24  6:37       ` Jan Beulich
2017-08-24 11:33         ` Zhongze Liu
2017-08-24 12:39           ` Jan Beulich
2017-08-24 14:30             ` Daniel De Graaf
2017-08-22 18:08 ` [PATCH 5/6] libxl: support mapping static shared memory areas during domain creation Zhongze Liu
2017-08-22 21:42   ` Stefano Stabellini
2017-08-23  2:37     ` Zhongze Liu
2017-08-25 11:05   ` Wei Liu
2017-08-25 12:02     ` Zhongze Liu
2017-08-25 12:09       ` Wei Liu
2017-08-22 18:08 ` [PATCH 6/6] libxl: support unmapping static shared memory areas during domain destruction Zhongze Liu
2017-08-22 21:31   ` Stefano Stabellini
2017-08-23  2:43     ` Zhongze Liu
2017-08-25 11:05   ` Wei Liu [this message]

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=20170825110548.e3ppbaxo4eh4esi6@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=blackskygg@gmail.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --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).