From: Miaohe Lin <linmiaohe@huawei.com>
To: David Hildenbrand <david@redhat.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm/memory_hotplug: use helper function zone_end_pfn() to get end_pfn
Date: Thu, 28 Jan 2021 09:58:57 +0800 [thread overview]
Message-ID: <029811ed-4988-769b-a9f4-7787cf0779c5@huawei.com> (raw)
In-Reply-To: <9e15556f-8535-d8ae-d5b1-db264d377c20@redhat.com>
Hi:
On 2021/1/27 17:40, David Hildenbrand wrote:
> On 27.01.21 10:32, Miaohe Lin wrote:
>> Commit 108bcc96ef70 ("mm: add & use zone_end_pfn() and zone_spans_pfn()")
>> introduced the helper zone_end_pfn() to calculate the zone end pfn. But
>> update_pgdat_span() forgot to use it. Use this helper and re-name local
>> variable zone_end_pfn to end_pfn to fix below compilation error:
>>
>> mm/memory_hotplug.c: In function ‘update_pgdat_span’:
>> mm/memory_hotplug.c:448:32: error: called object ‘zone_end_pfn’ is not a
>> function or function pointer
>> unsigned long zone_end_pfn = zone_end_pfn(zone);
>> ^~~~~~~~~~~~
>> mm/memory_hotplug.c:448:17: note: declared here
>> unsigned long zone_end_pfn = zone_end_pfn(zone);
>> ^~~~~~~~~~~~
>>
>
> Please don't talk about compilation issues your changes introduce in that detail, that's just confusing and looks like something would already be broken. Please simplify to something like
I will keep this in mind. Thanks.
>
> "Let's use zone_end_pfn(zone). We have to rename the local variable to avoid an identifier clash (variable vs. function)."
>
> With that
>
> Reviewed-by: David Hildenbrand <david@redhat.com>
>
Many thanks for review and reply.
>> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
>> ---
>> mm/memory_hotplug.c | 9 ++++-----
>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
>> index 710e469fb3a1..0483db52b85f 100644
>> --- a/mm/memory_hotplug.c
>> +++ b/mm/memory_hotplug.c
>> @@ -493,20 +493,19 @@ static void update_pgdat_span(struct pglist_data *pgdat)
>> for (zone = pgdat->node_zones;
>> zone < pgdat->node_zones + MAX_NR_ZONES; zone++) {
>> - unsigned long zone_end_pfn = zone->zone_start_pfn +
>> - zone->spanned_pages;
>> + unsigned long end_pfn = zone_end_pfn(zone);
>> /* No need to lock the zones, they can't change. */
>> if (!zone->spanned_pages)
>> continue;
>> if (!node_end_pfn) {
>> node_start_pfn = zone->zone_start_pfn;
>> - node_end_pfn = zone_end_pfn;
>> + node_end_pfn = end_pfn;
>> continue;
>> }
>> - if (zone_end_pfn > node_end_pfn)
>> - node_end_pfn = zone_end_pfn;
>> + if (end_pfn > node_end_pfn)
>> + node_end_pfn = end_pfn;
>> if (zone->zone_start_pfn < node_start_pfn)
>> node_start_pfn = zone->zone_start_pfn;
>> }
>>
>
>
prev parent reply other threads:[~2021-01-28 1:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 9:32 Miaohe Lin
2021-01-27 9:40 ` David Hildenbrand
2021-01-28 1:58 ` Miaohe Lin [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=029811ed-4988-769b-a9f4-7787cf0779c5@huawei.com \
--to=linmiaohe@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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