linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] PPC: Correct the tophys/tovirt macros
Date: Thu, 04 Oct 2012 21:19:04 +1000	[thread overview]
Message-ID: <1349349544.4260.24.camel@pasglop> (raw)
In-Reply-To: <20120930232847.GG30637@obsidianresearch.com>

On Sun, 2012-09-30 at 17:28 -0600, Jason Gunthorpe wrote:
> asm/page.h discusses the calculation for v2p and p2v, it should be:
>  va = pa + KERNELBASE - PHYSICAL_START
> which is the same as:
>  va = pa + LOAD_OFFSET
> 
> tophys/tovirt were using PAGE_OFFSET, which as page.h says, is almost
> always the same thing.
> 
> Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>

It's a bit gross tho in that KERNEL_BASE, PHYSICAL_START and LOAD_OFFSET
are about where the kernel is linked/running, and while the value ends
up happening to also be the p->v offset (and indeed not by accident), it
makes the code less clear and more confusing.

I think the main issue is that we did things wrong when implementing
non-0 based setups. PAGE_OFFSET should have remained what its name
implies which is the offset between p and v.

I don't have the bandwidth to revisit all that, but I really think that
whole are area where PAGE_OFFSET doesn't map 0 needs revisiting.

Ben.

> ---
>  arch/powerpc/include/asm/ppc_asm.h |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/powerpc/include/asm/ppc_asm.h b/arch/powerpc/include/asm/ppc_asm.h
> index ea2a86e..44edc3a 100644
> --- a/arch/powerpc/include/asm/ppc_asm.h
> +++ b/arch/powerpc/include/asm/ppc_asm.h
> @@ -461,14 +461,14 @@ END_FTR_SECTION_IFCLR(CPU_FTR_601)
>  #define fromreal(rd)	tovirt(rd,rd)
>  
>  #define tophys(rd,rs)				\
> -0:	addis	rd,rs,-PAGE_OFFSET@h;		\
> +0:	addis	rd,rs,-LOAD_OFFSET@h;		\
>  	.section ".vtop_fixup","aw";		\
>  	.align  1;				\
>  	.long   0b;				\
>  	.previous
>  
>  #define tovirt(rd,rs)				\
> -0:	addis	rd,rs,PAGE_OFFSET@h;		\
> +0:	addis	rd,rs,LOAD_OFFSET@h;		\
>  	.section ".ptov_fixup","aw";		\
>  	.align  1;				\
>  	.long   0b;				\

  reply	other threads:[~2012-10-04 11:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-30 23:28 [PATCH] PPC: Correct the tophys/tovirt macros Jason Gunthorpe
2012-10-04 11:19 ` Benjamin Herrenschmidt [this message]
2012-10-04 17:08   ` Jason Gunthorpe

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=1349349544.4260.24.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linuxppc-dev@lists.ozlabs.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).