linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Scott Wood <oss@buserror.net>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v2 0/7] powerpc/8xx: Optimisation of TLB handling for IMMR and RAM
Date: Wed, 11 May 2016 17:03:55 +0200 (CEST)	[thread overview]
Message-ID: <cover.1462052179.git.christophe.leroy@c-s.fr> (raw)

The purpose of this set of patches is to continue on TLB handling
optimisation on the 8xx with the handling of IMMR area as a
single 512k area instead of multiple 4k pages.

This set includes a rework of linear RAM mapping in order to not use
page table but direct linear mapping. The result is equivalent to the
use of BATs on other PPCs and it avoids reading the page table.

This set also includes a rework of the handling of PIN_TLB config
option. This option used to be linked to the quantity of RAM available.
It is now independant, users having only 8M memory can also use PIN_TLB.

Christophe Leroy (7):
  powerpc/8xx: Fix vaddr for IMMR early remap
  powerpc/8xx: Map IMMR area with 512k page at a fixed address
  powerpc/8xx: CONFIG_PIN_TLB unneeded for CONFIG_PPC_EARLY_DEBUG_CPM
  powerpc/8xx: unpin all TLBs before flushing
  powerpc/8xx: Don't use page table for linear memory space
  powerpc/8xx: Rework CONFIG_PIN_TLB handling
  powerpc/8xx: add CONFIG_PIN_TLB_IMMR

 arch/powerpc/Kconfig              |   5 ++
 arch/powerpc/Kconfig.debug        |   1 -
 arch/powerpc/include/asm/fixmap.h |   7 ++
 arch/powerpc/kernel/asm-offsets.c |   8 ++
 arch/powerpc/kernel/head_8xx.S    | 159 +++++++++++++++++++-------------------
 arch/powerpc/mm/8xx_mmu.c         | 131 +++++++++++++++++++++----------
 arch/powerpc/mm/mmu_decl.h        |  10 ++-
 arch/powerpc/sysdev/cpm_common.c  |  15 +++-
 8 files changed, 211 insertions(+), 125 deletions(-)

-- 
v2: Fixed a test in the 6/7
2.1.0

             reply	other threads:[~2016-05-11 15:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11 15:03 Christophe Leroy [this message]
2016-05-11 15:03 ` [PATCH v2 1/7] powerpc/8xx: Fix vaddr for IMMR early remap Christophe Leroy
2016-05-11 20:38   ` Scott Wood
2016-05-13  9:25     ` Christophe Leroy
2016-05-16 23:11       ` Scott Wood
2016-05-17 19:01         ` christophe leroy
2016-05-11 15:03 ` [PATCH v2 2/7] powerpc/8xx: Map IMMR area with 512k page at a fixed address Christophe Leroy
2016-05-11 15:04 ` [PATCH v2 3/7] powerpc/8xx: CONFIG_PIN_TLB unneeded for CONFIG_PPC_EARLY_DEBUG_CPM Christophe Leroy
2016-05-11 15:04 ` [PATCH v2 4/7] powerpc/8xx: unpin all TLBs before flushing Christophe Leroy
2016-05-11 15:04 ` [PATCH v2 5/7] powerpc/8xx: Don't use page table for linear memory space Christophe Leroy
2016-05-11 15:04 ` [PATCH v2 6/7] powerpc/8xx: Rework CONFIG_PIN_TLB handling Christophe Leroy
2016-05-11 15:04 ` [PATCH v2 7/7] powerpc/8xx: add CONFIG_PIN_TLB_IMMR Christophe Leroy

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=cover.1462052179.git.christophe.leroy@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=oss@buserror.net \
    --cc=paulus@samba.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).