All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
	will@kernel.org, "David Hildenbrand" <david@redhat.com>,
	catalin.marinas@arm.com, linux-kernel@vger.kernel.org,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"James Morse" <james.morse@arm.com>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Robin Murphy" <robin.murphy@arm.com>,
	ardb@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
Date: Mon, 4 Jan 2021 15:36:33 +0000	[thread overview]
Message-ID: <20210104153633.00003288@Huawei.com> (raw)
In-Reply-To: <1608621144-4001-2-git-send-email-anshuman.khandual@arm.com>

On Tue, 22 Dec 2020 12:42:23 +0530
Anshuman Khandual <anshuman.khandual@arm.com> wrote:

> pfn_valid() validates a pfn but basically it checks for a valid struct page
> backing for that pfn. It should always return positive for memory ranges
> backed with struct page mapping. But currently pfn_valid() fails for all
> ZONE_DEVICE based memory types even though they have struct page mapping.
> 
> pfn_valid() asserts that there is a memblock entry for a given pfn without
> MEMBLOCK_NOMAP flag being set. The problem with ZONE_DEVICE based memory is
> that they do not have memblock entries. Hence memblock_is_map_memory() will
> invariably fail via memblock_search() for a ZONE_DEVICE based address. This
> eventually fails pfn_valid() which is wrong. memblock_is_map_memory() needs
> to be skipped for such memory ranges. As ZONE_DEVICE memory gets hotplugged
> into the system via memremap_pages() called from a driver, their respective
> memory sections will not have SECTION_IS_EARLY set.
> 
> Normal hotplug memory will never have MEMBLOCK_NOMAP set in their memblock
> regions. Because the flag MEMBLOCK_NOMAP was specifically designed and set
> for firmware reserved memory regions. memblock_is_map_memory() can just be
> skipped as its always going to be positive and that will be an optimization
> for the normal hotplug memory. Like ZONE_DEVIE based memory, all hotplugged

typo: ZONE_DEVIE

> normal memory too will not have SECTION_IS_EARLY set for their sections.
> 
> Skipping memblock_is_map_memory() for all non early memory sections would
> fix pfn_valid() problem for ZONE_DEVICE based memory and also improve its
> performance for normal hotplug memory as well.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Fixes: 73b20c84d42d ("arm64: mm: implement pte_devmap support")
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
>  arch/arm64/mm/init.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index 75addb36354a..ee23bda00c28 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -225,6 +225,18 @@ int pfn_valid(unsigned long pfn)
>  
>  	if (!valid_section(__pfn_to_section(pfn)))
>  		return 0;
> +
> +	/*
> +	 * ZONE_DEVICE memory does not have the memblock entries.
> +	 * memblock_is_map_memory() check for ZONE_DEVICE based
> +	 * addresses will always fail. Even the normal hotplugged
> +	 * memory will never have MEMBLOCK_NOMAP flag set in their
> +	 * memblock entries. Skip memblock search for all non early
> +	 * memory sections covering all of hotplug memory including
> +	 * both normal and ZONE_DEVIE based.

Here as well + the cover letter title.

> +	 */
> +	if (!early_section(__pfn_to_section(pfn)))
> +		return 1;
>  #endif
>  	return memblock_is_map_memory(addr);
>  }


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"Mark Rutland" <mark.rutland@arm.com>,
	catalin.marinas@arm.com, "David Hildenbrand" <david@redhat.com>,
	"Robin Murphy" <robin.murphy@arm.com>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"James Morse" <james.morse@arm.com>,
	"Dan Williams" <dan.j.williams@intel.com>,
	will@kernel.org, ardb@kernel.org
Subject: Re: [RFC 1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE based memory
Date: Mon, 4 Jan 2021 15:36:33 +0000	[thread overview]
Message-ID: <20210104153633.00003288@Huawei.com> (raw)
In-Reply-To: <1608621144-4001-2-git-send-email-anshuman.khandual@arm.com>

On Tue, 22 Dec 2020 12:42:23 +0530
Anshuman Khandual <anshuman.khandual@arm.com> wrote:

> pfn_valid() validates a pfn but basically it checks for a valid struct page
> backing for that pfn. It should always return positive for memory ranges
> backed with struct page mapping. But currently pfn_valid() fails for all
> ZONE_DEVICE based memory types even though they have struct page mapping.
> 
> pfn_valid() asserts that there is a memblock entry for a given pfn without
> MEMBLOCK_NOMAP flag being set. The problem with ZONE_DEVICE based memory is
> that they do not have memblock entries. Hence memblock_is_map_memory() will
> invariably fail via memblock_search() for a ZONE_DEVICE based address. This
> eventually fails pfn_valid() which is wrong. memblock_is_map_memory() needs
> to be skipped for such memory ranges. As ZONE_DEVICE memory gets hotplugged
> into the system via memremap_pages() called from a driver, their respective
> memory sections will not have SECTION_IS_EARLY set.
> 
> Normal hotplug memory will never have MEMBLOCK_NOMAP set in their memblock
> regions. Because the flag MEMBLOCK_NOMAP was specifically designed and set
> for firmware reserved memory regions. memblock_is_map_memory() can just be
> skipped as its always going to be positive and that will be an optimization
> for the normal hotplug memory. Like ZONE_DEVIE based memory, all hotplugged

typo: ZONE_DEVIE

> normal memory too will not have SECTION_IS_EARLY set for their sections.
> 
> Skipping memblock_is_map_memory() for all non early memory sections would
> fix pfn_valid() problem for ZONE_DEVICE based memory and also improve its
> performance for normal hotplug memory as well.
> 
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Robin Murphy <robin.murphy@arm.com>
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
> Fixes: 73b20c84d42d ("arm64: mm: implement pte_devmap support")
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
>  arch/arm64/mm/init.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/arch/arm64/mm/init.c b/arch/arm64/mm/init.c
> index 75addb36354a..ee23bda00c28 100644
> --- a/arch/arm64/mm/init.c
> +++ b/arch/arm64/mm/init.c
> @@ -225,6 +225,18 @@ int pfn_valid(unsigned long pfn)
>  
>  	if (!valid_section(__pfn_to_section(pfn)))
>  		return 0;
> +
> +	/*
> +	 * ZONE_DEVICE memory does not have the memblock entries.
> +	 * memblock_is_map_memory() check for ZONE_DEVICE based
> +	 * addresses will always fail. Even the normal hotplugged
> +	 * memory will never have MEMBLOCK_NOMAP flag set in their
> +	 * memblock entries. Skip memblock search for all non early
> +	 * memory sections covering all of hotplug memory including
> +	 * both normal and ZONE_DEVIE based.

Here as well + the cover letter title.

> +	 */
> +	if (!early_section(__pfn_to_section(pfn)))
> +		return 1;
>  #endif
>  	return memblock_is_map_memory(addr);
>  }


  parent reply	other threads:[~2021-01-04 15:38 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22  7:12 [RFC 0/2] arm64/mm: Fix pfn_valid() for ZONE_DEVIE based memory Anshuman Khandual
2020-12-22  7:12 ` Anshuman Khandual
2020-12-22  7:12 ` [RFC 1/2] arm64/mm: Fix pfn_valid() for ZONE_DEVICE " Anshuman Khandual
2020-12-22  7:12   ` Anshuman Khandual
2020-12-22  9:11   ` David Hildenbrand
2020-12-22  9:11     ` David Hildenbrand
2021-01-04  6:18     ` Anshuman Khandual
2021-01-04  6:18       ` Anshuman Khandual
2021-01-11 10:31       ` David Hildenbrand
2021-01-11 10:31         ` David Hildenbrand
2021-01-11 14:00         ` Mike Rapoport
2021-01-11 14:00           ` Mike Rapoport
2021-01-04 15:36   ` Jonathan Cameron [this message]
2021-01-04 15:36     ` Jonathan Cameron
2021-01-05  3:25     ` Anshuman Khandual
2021-01-05  3:25       ` Anshuman Khandual
2021-01-25  6:22   ` Anshuman Khandual
2021-01-25  6:22     ` Anshuman Khandual
2021-01-25  7:31     ` Mike Rapoport
2021-01-25  7:31       ` Mike Rapoport
2021-01-27  3:46       ` Anshuman Khandual
2021-01-27  3:46         ` Anshuman Khandual
2021-01-25  9:13     ` David Hildenbrand
2021-01-25  9:13       ` David Hildenbrand
2021-01-27  4:06       ` Anshuman Khandual
2021-01-27  4:06         ` Anshuman Khandual
2021-01-27  9:29         ` David Hildenbrand
2021-01-27  9:29           ` David Hildenbrand
2021-01-28  7:42           ` Anshuman Khandual
2021-01-28  7:42             ` Anshuman Khandual
2020-12-22  7:12 ` [RFC 2/2] arm64/mm: Reorganize pfn_valid() Anshuman Khandual
2020-12-22  7:12   ` Anshuman Khandual

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=20210104153633.00003288@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=dan.j.williams@intel.com \
    --cc=david@redhat.com \
    --cc=james.morse@arm.com \
    --cc=jglisse@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robin.murphy@arm.com \
    --cc=will@kernel.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.