From: Jan Beulich <jbeulich@suse.com>
To: Hongyan Xia <hx242@xen.org>
Cc: xen-devel@lists.xenproject.org,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
"Andrew Cooper" <andrew.cooper3@citrix.com>
Subject: Re: [PATCH 3/5] x86_64/mm: map and unmap page tables in share_hotadd_m2p_table
Date: Tue, 7 Apr 2020 17:14:39 +0200 [thread overview]
Message-ID: <0d0fb4e9-c27e-a8b2-8fc7-602bc535b655@suse.com> (raw)
In-Reply-To: <7a5e9095c1c927819d248d5227d2511676781855.camel@xen.org>
On 07.04.2020 17:11, Hongyan Xia wrote:
> On Wed, 2020-04-01 at 14:29 +0200, Jan Beulich wrote:
>> On 23.03.2020 10:41, Hongyan Xia wrote:
>>> --- a/xen/include/asm-x86/page.h
>>> +++ b/xen/include/asm-x86/page.h
>>> @@ -196,6 +196,24 @@ static inline l4_pgentry_t
>>> l4e_from_paddr(paddr_t pa, unsigned int flags)
>>> #define map_l2t_from_l3e(x) (l2_pgentry_t
>>> *)map_domain_page(l3e_get_mfn(x))
>>> #define map_l3t_from_l4e(x) (l3_pgentry_t
>>> *)map_domain_page(l4e_get_mfn(x))
>>>
>>> +#define l1e_from_l2e(l2e, off) ({ \
>>> + l1_pgentry_t *l1t = map_l1t_from_l2e(l2e); \
>>> + l1_pgentry_t l1e = l1t[off]; \
>>> + UNMAP_DOMAIN_PAGE(l1t); \
>>> + l1e; })
>>> +
>>> +#define l2e_from_l3e(l3e, off) ({ \
>>> + l2_pgentry_t *l2t = map_l2t_from_l3e(l3e); \
>>> + l2_pgentry_t l2e = l2t[off]; \
>>> + UNMAP_DOMAIN_PAGE(l2t); \
>>> + l2e; })
>>> +
>>> +#define l3e_from_l4e(l4e, off) ({ \
>>> + l3_pgentry_t *l3t = map_l3t_from_l4e(l4e); \
>>> + l3_pgentry_t l3e = l3t[off]; \
>>> + UNMAP_DOMAIN_PAGE(l3t); \
>>> + l3e; })
>>
>> There's a reason these are macros rather than inline functions,
>> I assume? (This reason would be nice to be stated in the
>> description.)
>
> Actually no specific reasons, just to keep them as macros to be
> consistent with other helpers above. Fairly trivial to convert them
> into inline functions if this is desired.
Where possible this would be the preferred route for new helpers.
>> I don't see why you use UNMAP_DOMAIN_PAGE() rather than
>> unmap_domain_page() here - the variables in question go out of
>> scope right afterwards, so the storing of NULL into them is
>> pointless (and very likely to be eliminated by the compiler
>> anyway).
>
> My intention is to just avoid using the lower case one altogether, so
> that one day when we need to expand any function or macros we do not
> need to look back at the code and worry about whether any lower case
> ones need to be converted to upper case (sometimes for large functions
> this may not be trivial), and the compiler can deal with the extra
> nullification anyway.
I don't agree with this goal; perhaps others on Cc have an opinion?
Jan
next prev parent reply other threads:[~2020-04-07 15:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 9:41 [Xen-devel] [PATCH 0/5] use new API for Xen page tables Hongyan Xia
2020-03-23 9:41 ` [Xen-devel] [PATCH 1/5] x86/shim: map and unmap page tables in replace_va_mapping Hongyan Xia
2020-04-01 12:11 ` Jan Beulich
2020-03-23 9:41 ` [Xen-devel] [PATCH 2/5] x86_64/mm: map and unmap page tables in m2p_mapped Hongyan Xia
2020-04-01 12:19 ` Jan Beulich
2020-03-23 9:41 ` [Xen-devel] [PATCH 3/5] x86_64/mm: map and unmap page tables in share_hotadd_m2p_table Hongyan Xia
2020-04-01 12:29 ` Jan Beulich
2020-04-07 15:11 ` Hongyan Xia
2020-04-07 15:14 ` Jan Beulich [this message]
2020-04-08 9:32 ` Hongyan Xia
2020-03-23 9:41 ` [Xen-devel] [PATCH 4/5] x86_64/mm: map and unmap page tables in destroy_compat_m2p_mapping Hongyan Xia
2020-03-23 9:41 ` [Xen-devel] [PATCH 5/5] x86_64/mm: map and unmap page tables in destroy_m2p_mapping Hongyan Xia
2020-04-01 12:40 ` Jan Beulich
2020-04-07 16:23 ` Hongyan Xia
2020-03-29 15:06 ` [Xen-devel] [PATCH 0/5] use new API for Xen page tables Wei Liu
2020-03-30 8:25 ` Hongyan Xia
2020-04-06 8:27 ` Hongyan Xia
2020-04-06 11:03 ` Jan Beulich
2020-04-07 14:28 ` Hongyan Xia
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=0d0fb4e9-c27e-a8b2-8fc7-602bc535b655@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=hx242@xen.org \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--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 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).