From: David Hildenbrand <david@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>, linux-mm@kvack.org
Cc: Arnd Bergmann <arnd@arndb.de>,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/pgtable: Move extern zero_pfn outside __HAVE_COLOR_ZERO_PAGE
Date: Tue, 16 Jun 2020 09:39:07 +0200 [thread overview]
Message-ID: <f55dff2d-d32e-8de1-0177-e6ba713e0cd9@redhat.com> (raw)
In-Reply-To: <1592280498-15442-1-git-send-email-anshuman.khandual@arm.com>
On 16.06.20 06:08, Anshuman Khandual wrote:
> zero_pfn variable is required whether __HAVE_COLOR_ZERO_PAGE is enabled
Why is that relevant for this patch?
> or not. Also it should not really be declared individually in all functions
> where it gets used. Just move the declaration outside, which also makes it
> available for other potential users.
So, all you're essentially doing is exposing zero_pfn in pgtable.h now.
If everybody should just use my_zero_pfn(), I don't really see the
benefit of this patch, sorry.
>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: linux-arch@vger.kernel.org
> Cc: linux-mm@kvack.org
> Cc: linux-kernel@vger.kernel.org
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> Applies on 5.8-rc1. If the earlier motivation was to hide zero_pfn from
> general visibility, we could just put in a comment and update the commit
> message that my_zero_pfn() should always be used rather than zero_pfn.
> Build tested on many platforms and boot tested on arm64, x86.
>
> include/linux/pgtable.h | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/pgtable.h b/include/linux/pgtable.h
> index 32b6c52d41b9..078e9864abca 100644
> --- a/include/linux/pgtable.h
> +++ b/include/linux/pgtable.h
> @@ -1020,10 +1020,11 @@ extern void untrack_pfn(struct vm_area_struct *vma, unsigned long pfn,
> extern void untrack_pfn_moved(struct vm_area_struct *vma);
> #endif
>
> +extern unsigned long zero_pfn;
> +
> #ifdef __HAVE_COLOR_ZERO_PAGE
> static inline int is_zero_pfn(unsigned long pfn)
> {
> - extern unsigned long zero_pfn;
> unsigned long offset_from_zero_pfn = pfn - zero_pfn;
> return offset_from_zero_pfn <= (zero_page_mask >> PAGE_SHIFT);
> }
> @@ -1033,13 +1034,11 @@ static inline int is_zero_pfn(unsigned long pfn)
> #else
> static inline int is_zero_pfn(unsigned long pfn)
> {
> - extern unsigned long zero_pfn;
> return pfn == zero_pfn;
> }
>
> static inline unsigned long my_zero_pfn(unsigned long addr)
> {
> - extern unsigned long zero_pfn;
> return zero_pfn;
> }
> #endif
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-06-16 7:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-16 4:08 Anshuman Khandual
2020-06-16 5:24 ` Anshuman Khandual
2020-06-16 7:39 ` David Hildenbrand [this message]
2020-06-16 9:48 ` Anshuman Khandual
2020-06-16 10:04 ` David Hildenbrand
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=f55dff2d-d32e-8de1-0177-e6ba713e0cd9@redhat.com \
--to=david@redhat.com \
--cc=anshuman.khandual@arm.com \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--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