linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	lftan@altera.com, jonas@southpole.se, will.deacon@arm.com
Subject: Re: [PATCH resend 0/3] mm: allow arch to override lowmem_page_address
Date: Thu, 21 Apr 2016 16:51:38 -0700	[thread overview]
Message-ID: <20160421165138.a57be293ec370d5ea014e1ae@linux-foundation.org> (raw)
In-Reply-To: <1460995497-24312-1-git-send-email-ard.biesheuvel@linaro.org>

On Mon, 18 Apr 2016 18:04:54 +0200 Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:

> These patches allow the arch to define the page_to_virt() conversion that
> is used in lowmem_page_address(). This is desirable for arm64, where this
> conversion is trivial when CONFIG_SPARSEMEM_VMEMMAP is enabled, while
> breaking it up into __va(PFN_PHYS(page_to_pfn(page))), as is done currently
> in lowmem_page_address(), will force the use of a virt-to-phys() conversion
> and back again, which always involves a memory access on arm64, since the
> start of physical memory is not a compile time constant.
> 
> I have split off these patches from my series 'arm64: optimize virt_to_page
> and page_address' which I sent out 3 weeks ago, and resending them in the
> hope that they can be picked up (with Will's ack on #3) to be merged via
> the mm tree.
> 
> I have cc'ed the nios2 and openrisc maintainers on previous versions, and
> cc'ing them again now. I have dropped both of the arch specific mailing
> lists, since one is defunct and the other is subscriber only.
> 
> Andrew, is this something you would be pulling to pick up (assuming that you
> agree with the contents)? Thanks.

Looks OK to me and apart from the trivial openrisc/nios2 changes it's
obviously a no-op for all-but-arm.  So I suggest you include these
patches in the appropriate arm tree.

Acked-by: Andrew Morton <akpm@linux-foundation.org>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2016-04-21 23:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 16:04 [PATCH resend 0/3] mm: allow arch to override lowmem_page_address Ard Biesheuvel
2016-04-18 16:04 ` [PATCH resend 1/3] nios2: use correct void* return type for page_to_virt() Ard Biesheuvel
2016-04-19  9:35   ` Ley Foon Tan
2016-04-18 16:04 ` [PATCH resend 2/3] openrisc: drop wrongly typed definition of page_to_virt() Ard Biesheuvel
2016-04-18 16:04 ` [PATCH resend 3/3] mm: replace open coded page to virt conversion with page_to_virt() Ard Biesheuvel
2016-04-18 16:07 ` [PATCH resend 0/3] mm: allow arch to override lowmem_page_address Ard Biesheuvel
2016-04-21 23:51 ` Andrew Morton [this message]
2016-04-22  9:07   ` Will Deacon

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=20160421165138.a57be293ec370d5ea014e1ae@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=ard.biesheuvel@linaro.org \
    --cc=jonas@southpole.se \
    --cc=lftan@altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).