From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Zhongze Liu <blackskygg@gmail.com>
Cc: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
edgari@xilinx.com, xen-devel@lists.xenproject.org,
Jarvis Roach <Jarvis.Roach@dornerworks.com>
Subject: Re: [RFC v2]Proposal to allow setting up shared memory areas between VMs from xl config file
Date: Fri, 23 Jun 2017 10:16:52 +0100 [thread overview]
Message-ID: <e1f98758-377b-2ea4-31f5-1e0435264fc4@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1706221358550.12819@sstabellini-ThinkPad-X260>
Hi,
On 22/06/17 22:05, Stefano Stabellini wrote:
>> When we encounter an id IDx during "xl create":
>>
>> + If it’s not under /local/shared_mem:
>> + If the corresponding entry has a "master" tag, create the
>> corresponding entries for IDx in xenstore
>> + If there isn't a "master" tag, say error.
>>
>> + If it’s found under /local/shared_mem:
>> + If the corresponding entry has a "master" tag, say error
>> + If there isn't a "master" tag, map the pages to the newly
>> created domain, and add the current domain and necessary information
>> under /local/shared_mem/IDx/slaves.
>
> Aside from using "gfn" instead of gmfn everywhere, I think it looks
> pretty good.
>
> I would leave out permissions and cacheability attributes from this
> version of the work. I would just add a note saying that memory will be
> mapped as RW regular cacheable RAM. Other permissions and cacheability
> will be possible, but they are not implemented yet.
Well, I think we should design the interface correctly from the
beginning to facilitate future extension.
Also, you need to clarify what you mean by "regular cacheable RAM". Are
they write-through, write-back...? But, on ARM, this would only be the
caching attribute in stage-2 page table. The final caching, memory type,
shareability would be a combination of stage-2 and stage-1 attributes.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-23 9:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 17:18 [RFC v2]Proposal to allow setting up shared memory areas between VMs from xl config file Zhongze Liu
2017-06-20 17:29 ` Julien Grall
2017-06-22 16:58 ` Zhongze Liu
2017-06-22 20:55 ` Stefano Stabellini
2017-06-21 15:09 ` Wei Liu
2017-06-21 15:12 ` Julien Grall
2017-06-22 17:27 ` Zhongze Liu
2017-06-22 18:55 ` Zhongze Liu
2017-06-28 16:03 ` Wei Liu
2017-06-22 21:05 ` Stefano Stabellini
2017-06-23 9:16 ` Julien Grall [this message]
2017-06-23 18:21 ` Stefano Stabellini
2017-06-23 19:19 ` Jarvis Roach
2017-06-23 20:09 ` Stefano Stabellini
2017-06-23 20:47 ` Jarvis Roach
2017-06-23 20:18 ` Julien Grall
2017-07-18 12:10 ` Julien Grall
2017-07-18 14:22 ` Zhongze Liu
2017-07-18 16:13 ` 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=e1f98758-377b-2ea4-31f5-1e0435264fc4@arm.com \
--to=julien.grall@arm.com \
--cc=Jarvis.Roach@dornerworks.com \
--cc=blackskygg@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=edgari@xilinx.com \
--cc=ian.jackson@eu.citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.