linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Better virt_to_page() handling
Date: Fri, 28 Mar 2014 20:05:40 +0000	[thread overview]
Message-ID: <20140328200540.GQ7528@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.11.1403281506250.1571@knanqh.ubzr>

On Fri, Mar 28, 2014 at 03:52:16PM -0400, Nicolas Pitre wrote:
> I see it might be hard to make the last two common, unless it is defined 
> up front and the odd case does a #undef virt_to_pfn before redefining 
> it.  Which way is best I'm not sure.

Given the problems we've had in this area with changes ending up with
build failures, I think it's far better to have simplicity even if it
means duplicating definitions, rather than trying to invent some clever
way to avoid duplications.

We've had soo many build failures due to trying to be too clever that
I'm not playing the "try to be clever" game here anymore.  We can be
more verbose instead.

> Also this needs to take care of those machines overriding PHYS_OFFSET at 
> run time (see commit a77e0c7b2774f).

Platforms don't override PHYS_OFFSET.  They override PLAT_PHYS_OFFSET
instead.

> However it looks like no code 
> relying on the LPAE version of early_paging_init() has been merged in 
> mainline yet.

I believe that's fully reliant on CONFIG_ARM_PATCH_PHYS_VIRT being set,
and the difference for that case would be setting __pv_phys_pfn_offset
instead of __pv_phys_offset, which is a simple modification.

However, that's something which should be done by core code, not
individually by platforms.  Since we don't have any view of code doing
this yet, it's not relevant here.  We can only deal with what is in
mainline and not in external trees.

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-03-28 20:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 15:28 __pv_phys_offset, inline assembly functions, and such like Russell King - ARM Linux
2014-03-28 15:29 ` [PATCH] ARM: Better virt_to_page() handling Russell King
2014-03-28 19:52   ` Nicolas Pitre
2014-03-28 20:05     ` Russell King - ARM Linux [this message]
2014-03-29  2:51       ` Nicolas Pitre
2014-04-22 19:55   ` Ezequiel Garcia
2014-04-23  7:35     ` [PATCH] ARM: Fix double definition of virt_to_pfn() Peter Ujfalusi
2014-04-23  9:37       ` Russell King - ARM Linux
2014-04-23 10:40         ` Peter Ujfalusi
2014-03-28 16:44 ` __pv_phys_offset, inline assembly functions, and such like Arnd Bergmann
2014-03-28 16:56   ` Russell King - ARM Linux
2014-03-28 17:39     ` Arnd Bergmann
2014-04-04 22:32 ` [PATCH] ARM: Better virt_to_page() handling Russell King
2014-04-04 22:44   ` Russell King - ARM Linux

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=20140328200540.GQ7528@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).