From: Zhongze Liu <blackskygg@gmail.com>
To: Julien Grall <julien.grall@arm.com>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v4 4/7] libxl: support mapping static shared memory areas during domain creation
Date: Tue, 6 Feb 2018 23:59:19 +0800 [thread overview]
Message-ID: <CAHrd_jrTUaNwD3YEaqFvqSHACouOq=tK19rk3GCTK2GBkd70mw@mail.gmail.com> (raw)
In-Reply-To: <6eb51518-4e01-1d4a-e345-a0fc91c3594c@arm.com>
Hi Julien,
2018-02-06 21:07 GMT+08:00 Julien Grall <julien.grall@arm.com>:
> Hi,
>
> On 01/30/2018 05:50 PM, Zhongze Liu wrote:
>>
>> Add libxl__sshm_add to map shared pages from one DomU to another, The
>> mapping
>> process involves the follwing steps:
[...]
>> +
>> +/* Set default values for libxl_static_shm */
>> +int libxl__sshm_setdefault(libxl__gc *gc, uint32_t domid,
>> + libxl_static_shm *sshm)
>> +{
>> + int rc;
>> +
>> + if (sshm->role == LIBXL_SSHM_ROLE_UNKNOWN)
>> + sshm->role = LIBXL_SSHM_ROLE_SLAVE;
>> + if (sshm->prot == LIBXL_SSHM_PROT_UNKNOWN)
>> + sshm->prot = LIBXL_SSHM_PROT_RW;
>
>
> What is the purpose of {ROLE,PROT}_UNKNOWN if you default it resp. to
> ROLE_SLAVE and PROT_RW. Would not it be easier to just drop them?
The *_UNKNOWN values are used by the libxlu code to check whether a specific
option was set more than once. Without the default *_UNKNOWN value, I will not
be able to judge if, say, role is set to 'slave' by the user or not,
and therefore, if I
see the user setting role to 'master', I won't be able to tell if role
is specified twice
or not.
I think treating re-specification of options as errors will be good
for the users.
[...]
>> +
>> +/* libxl__sshm_do_map -- map pages into slave's physmap
>> + *
>> + * This functions maps
>> + * master gfn: [@msshm->begin + @sshm->offset, @msshm->end +
>> @sshm->offset)
>> + * into
>> + * slave gfn: [@sshm->begin, @sshm->end)
>> + *
>> + * The gfns of the pages that are successfully mapped will be stored
>> + * in @mapped, and the number of the gfns will be stored in @nmapped.
>> + *
>> + * The caller have to guarentee that sshm->begin < sshm->end and all
>> the
>
>
> s/have to/has to/ I think.
> s/guarentee/guarantee/
>
>> + * values are page-aligned.
>
>
> Hmmm, I don't see the alignement check in libxl. So do you rely on the
> toolstack to do it?
Yes, This was done in libxlu_sshm.c.
Cheers,
Zhongze Liu
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-06 15:59 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 17:50 [PATCH v4 0/7] Allow setting up shared memory areas between VMs from xl config files Zhongze Liu
2018-01-30 17:50 ` [PATCH v4 1/7] libxc: add xc_domain_remove_from_physmap to wrap XENMEM_remove_from_physmap Zhongze Liu
2018-01-30 17:50 ` [PATCH v4 2/7] xen: xsm: flask: introduce XENMAPSPACE_gmfn_share for memory sharing Zhongze Liu
2018-02-01 10:23 ` Jan Beulich
2018-02-01 18:11 ` Zhongze Liu
2018-02-02 8:32 ` Jan Beulich
2018-02-05 9:59 ` Zhongze Liu
2018-02-13 15:15 ` Zhongze Liu
2018-02-13 15:26 ` Jan Beulich
2018-02-14 7:15 ` Zhongze Liu
2018-02-14 8:37 ` Jan Beulich
2018-02-14 17:02 ` Zhongze Liu
2018-02-15 8:58 ` Jan Beulich
2018-02-24 2:50 ` Zhongze Liu
2018-02-24 5:37 ` Zhongze Liu
2018-02-26 7:53 ` Jan Beulich
2018-02-06 11:04 ` Julien Grall
2018-01-30 17:50 ` [PATCH v4 3/7] libxl: introduce a new structure to represent static shared memory regions Zhongze Liu
2018-02-06 11:27 ` Julien Grall
2018-02-06 15:41 ` Zhongze Liu
2018-02-06 15:46 ` Julien Grall
2018-02-06 16:06 ` Zhongze Liu
2018-02-06 17:23 ` Julien Grall
2018-01-30 17:50 ` [PATCH v4 4/7] libxl: support mapping static shared memory areas during domain creation Zhongze Liu
2018-02-06 13:07 ` Julien Grall
2018-02-06 15:59 ` Zhongze Liu [this message]
2018-02-06 17:30 ` Julien Grall
2018-02-06 17:47 ` Wei Liu
2018-02-12 15:08 ` Zhongze Liu
2018-02-14 14:26 ` Wei Liu
2018-01-30 17:50 ` [PATCH v4 5/7] libxl: support unmapping static shared memory areas during domain destruction Zhongze Liu
2018-02-06 13:24 ` Julien Grall
2018-02-06 18:06 ` Wei Liu
2018-02-07 16:27 ` Zhongze Liu
2018-02-07 16:54 ` Julien Grall
2018-02-12 14:52 ` Zhongze Liu
2018-02-12 15:09 ` Julien Grall
2018-02-12 15:17 ` Zhongze Liu
2018-02-12 15:24 ` Julien Grall
2018-02-14 14:35 ` Wei Liu
2018-02-14 14:39 ` Wei Liu
2018-02-26 12:08 ` Ian Jackson
2018-01-30 17:50 ` [PATCH v4 6/7] libxl:xl: add parsing code to parse "libxl_static_sshm" from xl config files Zhongze Liu
2018-01-30 17:50 ` [PATCH v4 7/7] docs: documentation about static shared memory regions Zhongze Liu
2018-02-06 13:28 ` 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='CAHrd_jrTUaNwD3YEaqFvqSHACouOq=tK19rk3GCTK2GBkd70mw@mail.gmail.com' \
--to=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).