From: Zhongze Liu <blackskygg@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Julien Grall <julien.grall@arm.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>
Subject: Re: [PATCH v3 2/7] xsm: flask: change the dummy xsm policy and flask hook for map_gmfn_foregin
Date: Mon, 23 Oct 2017 17:54:51 +0800 [thread overview]
Message-ID: <CAHrd_jq48Bd6E8csLFXA8p6Mqu2JSzjBnNAF8HrL3s0yYAK1gQ@mail.gmail.com> (raw)
In-Reply-To: <59EDB5BB020000780018930F@prv-mh.provo.novell.com>
Hi Jan,
2017-10-23 15:26 GMT+08:00 Jan Beulich <JBeulich@suse.com>:
>>>> On 22.10.17 at 13:21, <blackskygg@gmail.com> wrote:
>> How about changing the policy to (c over d) && ((d over t) || (c over t))?
>> Given that (c over d) is a must, which is always checked somewhere higher
>> in the call stack as Daniel pointed out, permitting (d over t) or (c
>> over t) actually infers
>> permitting the other.
>>
>> - if you permit (d over t) but not (c over t):
>> Given (c over t),
>> (c) can first map the src page from (t) into its own memory space and then map
>> this page from its own memory space to (d)'s memory space.
>
> Would that work? The page, when in (c)'s space, is still owned by (t),
> so I don't see how mapping into (d)'s space could become possible
> just because it's mapped into (c)'s.
Yes, indeed. This won't work. Sorry for giving a wrong example here.
I think I now agree to add a new subop, too.
Cheers,
Zhongze Liu
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-10-23 9:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 2:36 [PATCH v3 0/7] Allow setting up shared memory areas between VMs from xl config files Zhongze Liu
2017-10-19 2:36 ` [PATCH v3 1/7] libxc: add xc_domain_remove_from_physmap to wrap XENMEM_remove_from_physmap Zhongze Liu
2017-10-31 12:40 ` Wei Liu
2017-10-19 2:36 ` [PATCH v3 2/7] xsm: flask: change the dummy xsm policy and flask hook for map_gmfn_foregin Zhongze Liu
2017-10-19 11:58 ` Jan Beulich
2017-10-19 17:36 ` Daniel De Graaf
2017-10-20 6:14 ` Jan Beulich
2017-10-20 13:34 ` Daniel De Graaf
2017-10-22 11:21 ` Zhongze Liu
2017-10-23 7:26 ` Jan Beulich
2017-10-23 9:54 ` Zhongze Liu [this message]
2017-10-25 9:37 ` Zhongze Liu
2017-10-25 15:36 ` Zhongze Liu
2017-10-26 6:41 ` Jan Beulich
2017-10-19 17:36 ` Daniel De Graaf
2017-10-20 0:34 ` Zhongze Liu
2017-10-20 0:55 ` Zhongze Liu
2017-10-20 13:02 ` Daniel De Graaf
2017-10-19 2:36 ` [PATCH v3 3/7] libxl: introduce a new structure to represent static shared memory regions Zhongze Liu
2017-10-31 12:48 ` Wei Liu
2017-10-19 2:36 ` [PATCH v3 4/7] libxl: support mapping static shared memory areas during domain creation Zhongze Liu
2017-11-01 15:55 ` Wei Liu
2017-11-09 0:48 ` Zhongze Liu
2017-10-19 2:36 ` [PATCH v3 5/7] libxl: support unmapping static shared memory areas during domain destruction Zhongze Liu
2017-11-01 15:55 ` Wei Liu
2017-11-09 2:06 ` Zhongze Liu
2017-11-09 2:10 ` Zhongze Liu
2017-10-19 2:36 ` [PATCH v3 6/7] libxl:xl: add parsing code to parse "libxl_static_sshm" from xl config files Zhongze Liu
2017-10-19 2:36 ` [PATCH v3 7/7] docs: documentation about static shared memory regions Zhongze Liu
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=CAHrd_jq48Bd6E8csLFXA8p6Mqu2JSzjBnNAF8HrL3s0yYAK1gQ@mail.gmail.com \
--to=blackskygg@gmail.com \
--cc=JBeulich@suse.com \
--cc=dgdegra@tycho.nsa.gov \
--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).