From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Correct virt_addr_valid
Date: Wed, 11 Dec 2013 10:44:29 +0000 [thread overview]
Message-ID: <20131211104429.GE26730@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <1386724982-16997-2-git-send-email-lauraa@codeaurora.org>
On Wed, Dec 11, 2013 at 01:23:02AM +0000, Laura Abbott wrote:
> The definition of virt_addr_valid is that virt_addr_valid should
> return true if and only if virt_to_page returns a valid pointer.
> The current definition of virt_addr_valid only checks against the
> virtual address range. There's no guarantee that just because a
> virtual address falls bewteen PAGE_OFFSET and high_memory the
> associated physical memory has a valid backing struct page. Follow
> the example of other architectures and convert to pfn_valid to
> verify that the virtual address is actually valid.
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Nicolas Pitre <nico@linaro.org>
> Signed-off-by: Laura Abbott <lauraa@codeaurora.org>
> ---
> arch/arm64/include/asm/memory.h | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/include/asm/memory.h b/arch/arm64/include/asm/memory.h
> index 3776217..9dc5dc3 100644
> --- a/arch/arm64/include/asm/memory.h
> +++ b/arch/arm64/include/asm/memory.h
> @@ -146,8 +146,7 @@ static inline void *phys_to_virt(phys_addr_t x)
> #define ARCH_PFN_OFFSET PHYS_PFN_OFFSET
>
> #define virt_to_page(kaddr) pfn_to_page(__pa(kaddr) >> PAGE_SHIFT)
> -#define virt_addr_valid(kaddr) (((void *)(kaddr) >= (void *)PAGE_OFFSET) && \
> - ((void *)(kaddr) < (void *)high_memory))
> +#define virt_addr_valid(kaddr) pfn_valid(__pa(kaddr) >> PAGE_SHIFT)
Hmm, this is pretty expensive on both arm and arm64, since we end up doing a
binary search through all of the memblocks.
Are you seeing real problems with the current code?
Will
next prev parent reply other threads:[~2013-12-11 10:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 1:23 [PATCH] arm: Correct virt_addr_valid Laura Abbott
2013-12-11 1:23 ` [PATCH] arm64: " Laura Abbott
2013-12-11 10:44 ` Will Deacon [this message]
2013-12-11 11:06 ` Russell King - ARM Linux
2013-12-11 17:26 ` Will Deacon
2013-12-11 21:13 ` Russell King - ARM Linux
2013-12-12 17:57 ` Catalin Marinas
2013-12-12 18:02 ` Russell King - ARM Linux
2013-12-12 22:09 ` Laura Abbott
2013-12-13 11:57 ` Catalin Marinas
2013-12-16 18:28 ` Laura Abbott
2013-12-17 14:19 ` Catalin Marinas
2013-12-11 17:35 ` Laura Abbott
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=20131211104429.GE26730@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).