From: Greg Ungerer <gerg@uclinux.org>
To: Steven King <sfking@fdwdc.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, linux-m68k@vger.kernel.org
Subject: Re: [PATCH] m68knommu: Correct page_to_phys when PAGE_OFFSET is non-zero.
Date: Fri, 20 Jun 2014 15:16:19 +1000 [thread overview]
Message-ID: <53A3C3A3.6040007@uclinux.org> (raw)
In-Reply-To: <201406112001.10513.sfking@fdwdc.com>
Hi Steven,
On 12/06/14 13:01, Steven King wrote:
> The definition of page_to_phys for nommu produces an incorrect value when
> PAGE_OFFSET is non-zero. The nommu version of page_to_pfn works correctly
> for non-zero PAGE_OFFSET, so use that instead.
>
> Signed-off-by: Steven King <sfking@fdwdc.com>
Looks good, thanks. Applied to m68knommu git tree, for-next branch.
Regards
Greg
> ---
> arch/m68k/include/asm/virtconvert.h | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/arch/m68k/include/asm/virtconvert.h b/arch/m68k/include/asm/virtconvert.h
> index f35229b..b8a82fb 100644
> --- a/arch/m68k/include/asm/virtconvert.h
> +++ b/arch/m68k/include/asm/virtconvert.h
> @@ -26,16 +26,12 @@ static inline void *phys_to_virt(unsigned long address)
> }
>
> /* Permanent address of a page. */
> -#ifdef CONFIG_MMU
> -#ifdef CONFIG_SINGLE_MEMORY_CHUNK
> +#if defined(CONFIG_MMU) && defined(CONFIG_SINGLE_MEMORY_CHUNK)
> #define page_to_phys(page) \
> __pa(PAGE_OFFSET + (((page) - pg_data_map[0].node_mem_map) << PAGE_SHIFT))
> #else
> #define page_to_phys(page) (page_to_pfn(page) << PAGE_SHIFT)
> #endif
> -#else
> -#define page_to_phys(page) (((page) - mem_map) << PAGE_SHIFT)
> -#endif
>
> /*
> * IO bus memory addresses are 1:1 with the physical address,
>
prev parent reply other threads:[~2014-06-20 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 3:01 [PATCH] m68knommu: Correct page_to_phys when PAGE_OFFSET is non-zero Steven King
2014-06-20 5:16 ` Greg Ungerer [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=53A3C3A3.6040007@uclinux.org \
--to=gerg@uclinux.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=sfking@fdwdc.com \
/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