linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mohun106@gmail.com (mohun106 at gmail.com)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/2] arm64: Add support for 48-bit Physical Addresses
Date: Wed, 27 Nov 2013 13:04:23 +0530	[thread overview]
Message-ID: <1385537665-5909-1-git-send-email-mohun106@gmail.com> (raw)

From: Radha Mohan Chintakuntla <rchintakuntla@cavium.com>

This patch series provides an implementation of supporting 48-bit
Physical Addresses for ARMv8 platforms. It is the maximum width that
any ARMv8 based processor can support. 

The implementation extends the existing support of 40-bit PA.The kernel
and user space will now be able to access 128TB each. With 4KB page size
the Linux now will be using 4 levels of page tables by making use of
'pud'. And with 64KB page size the Linux will be using 3 levels of page
tables.

The code has been tested with LTP.

Radha Mohan Chintakuntla (2):
  arm64: Add support for 48-bit Physical Addresses
  arm64: Add 48-bit PA support for 64KB page size

 arch/arm64/include/asm/memory.h               |    6 +--
 arch/arm64/include/asm/page.h                 |    4 +-
 arch/arm64/include/asm/pgalloc.h              |   20 ++++++-
 arch/arm64/include/asm/pgtable-3level-hwdef.h |   34 ++++++++++++
 arch/arm64/include/asm/pgtable-4level-hwdef.h |   57 ++++++++++++++++++++
 arch/arm64/include/asm/pgtable-4level-types.h |   71 +++++++++++++++++++++++++
 arch/arm64/include/asm/pgtable-hwdef.h        |    9 ++--
 arch/arm64/include/asm/pgtable.h              |   50 +++++++++++++++---
 arch/arm64/include/asm/tlb.h                  |    2 -
 arch/arm64/kernel/head.S                      |   55 +++++++++++++++++--
 arch/arm64/kernel/traps.c                     |    7 +++
 arch/arm64/mm/proc.S                          |    2 +-
 12 files changed, 289 insertions(+), 28 deletions(-)
 create mode 100644 arch/arm64/include/asm/pgtable-4level-hwdef.h
 create mode 100644 arch/arm64/include/asm/pgtable-4level-types.h

             reply	other threads:[~2013-11-27  7:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  7:34 mohun106 at gmail.com [this message]
2013-11-27  7:34 ` [RFC PATCH 1/2] arm64: Add 48-bit PA support for 4KB page size mohun106 at gmail.com
2013-11-27 11:14   ` Mark Rutland
2013-11-27 16:00     ` Radha Mohan
2013-11-27  7:34 ` [RFC PATCH 2/2] arm64: Add 48-bit PA support for 64KB " mohun106 at gmail.com
2013-11-27 11:30   ` Mark Rutland
2013-11-27 11:04 ` [RFC PATCH 0/2] arm64: Add support for 48-bit Physical Addresses Marc Zyngier
2013-11-27 15:33   ` Radha Mohan
2013-11-27 15:50     ` Will Deacon
2013-11-27 17:59     ` Marc Zyngier
2013-11-28  2:14       ` Radha Mohan
2013-12-05 14:35         ` Radha Mohan
2013-12-05 15:10           ` Marc Zyngier
2013-12-05 17:30           ` Catalin Marinas
2013-12-10 16:53             ` Radha Mohan
2013-12-10 17:02               ` Catalin Marinas
2013-12-11  9:18                 ` Radha Mohan
2013-12-05 16:53         ` Catalin Marinas
2013-11-28  9:29 ` Steve Capper

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=1385537665-5909-1-git-send-email-mohun106@gmail.com \
    --to=mohun106@gmail.com \
    --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).