Skip to contentSkip to conversation

ARM64 HugePages for linux-next

DISCUSSION Steve Capper 2 participants 2 messages Jun 14, 2013 – Jun 17, 2013 Linux-next tree

lore
Share & tools
lore
#0 lore raw

Hello,
I've been working on a patch set to add huge page support to ARM64, this includes some changes to mm and x86. I've been advised by Andrew Morton to get these into linux-next asap:
http://marc.info/?l=linux-mm&m=137115843813005&w=2

Would it please be possible to have the patches from the git repo below pulled directly into linux-next?

(I've just merged them against linux-next/master and they build and run fine for me in an ARM64 Fast Model).

Thanks,

Signature · 48 lines
Steve

--->8

The following changes since commit d683b96b072dc4680fc74964eca77e6a23d1fa6e:

  Linux 3.10-rc4 (2013-06-02 17:11:17 +0900)

are available in the git repository at:

  git://git.linaro.org/people/stevecapper/linux.git for-next/hugepages

for you to fetch changes up to af07484863e0c20796081e57093886c22dc16705:

  ARM64: mm: THP support. (2013-06-14 09:52:41 +0100)

----------------------------------------------------------------
Steve Capper (11):
      mm: hugetlb: Copy huge_pmd_share from x86 to mm.
      x86: mm: Remove x86 version of huge_pmd_share.
      mm: hugetlb: Copy general hugetlb code from x86 to mm.
      x86: mm: Remove general hugetlb code from x86.
      mm: thp: Correct the HPAGE_PMD_ORDER check.
      ARM64: mm: Restore memblock limit when map_mem finished.
      ARM64: mm: Make PAGE_NONE pages read only and no-execute.
      ARM64: mm: Move PTE_PROT_NONE bit.
      ARM64: mm: HugeTLB support.
      ARM64: mm: Raise MAX_ORDER for 64KB pages and THP.
      ARM64: mm: THP support.

 arch/arm64/Kconfig                     |  17 +++
 arch/arm64/include/asm/hugetlb.h       | 117 ++++++++++++++++++
 arch/arm64/include/asm/pgtable-hwdef.h |  12 ++
 arch/arm64/include/asm/pgtable.h       |  96 ++++++++++++---
 arch/arm64/include/asm/tlb.h           |   6 +
 arch/arm64/include/asm/tlbflush.h      |   2 +
 arch/arm64/mm/Makefile                 |   1 +
 arch/arm64/mm/fault.c                  |  19 +--
 arch/arm64/mm/hugetlbpage.c            |  70 +++++++++++
 arch/arm64/mm/mmu.c                    |  19 ++-
 arch/x86/Kconfig                       |   6 +
 arch/x86/mm/hugetlbpage.c              | 187 ----------------------------
 include/linux/huge_mm.h                |   2 +-
 include/linux/hugetlb.h                |   4 +
 mm/hugetlb.c                           | 219 +++++++++++++++++++++++++++++++--
 15 files changed, 543 insertions(+), 234 deletions(-)
 create mode 100644 arch/arm64/include/asm/hugetlb.h
 create mode 100644 arch/arm64/mm/hugetlbpage.c
#1 lore raw

Hi Steve,

Quoted 8 lines · On Fri, 14 Jun 2013 12:29:09 +0100 Steve Capper <[email protected]> wrote:

I've been working on a patch set to add huge page support to ARM64, this includes some changes to mm and x86. I've been advised by Andrew Morton to get these into linux-next asap:
http://marc.info/?l=linux-mm&m=137115843813005&w=2

Would it please be possible to have the patches from the git repo below pulled directly into linux-next?

Added from today with you as contact and called arm64-hugepages.

Quoted 2 lines

(I've just merged them against linux-next/master and they build and run fine for me in an ARM64 Fast Model).

Thanks for testing that.

Thanks for adding your subsystem tree as a participant of linux-next. As you may know, this is not a judgment of your code. The purpose of linux-next is for integration testing and to lower the impact of conflicts between subsystems in the next merge window.

You will need to ensure that the patches/commits in your tree/series have been:
* submitted under GPL v2 (or later) and include the Contributor's Signed-off-by,
* posted to the relevant mailing list,
* reviewed by you (or another maintainer of your subsystem tree),
* successfully unit tested, and
* destined for the current or next Linux merge window.

Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary.

Signature · 15 lines
Cheers,
Stephen Rothwell 
[email protected]

Legal Stuff:
By participating in linux-next, your subsystem tree contributions are
public and will be included in the linux-next trees.  You may be sent
e-mail messages indicating errors or other issues when the
patches/commits from your subsystem tree are merged and tested in
linux-next.  These messages may also be cross-posted to the linux-next
mailing list, the linux-kernel mailing list, etc.  The linux-next tree
project and IBM (my employer) make no warranties regarding the linux-next
project, the testing procedures, the results, the e-mails, etc.  If you
don't agree to these ground rules, let me know and I'll remove your tree
from participation in linux-next.