linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>,
	linux-mips <linux-mips@linux-mips.org>
Subject: [PATCH 0/2] MIPS: Put PGD in C0_CONTEXT for 64-bit R2 processors.
Date: Wed, 14 Oct 2009 12:15:31 -0700	[thread overview]
Message-ID: <4AD62353.2080603@caviumnetworks.com> (raw)

This set of patches optimizes TLB handling in mips64r2 processors.  If
we have the mips64r2 ISA available, we can do enough bit twiddling
with out using a scratch register that it become possible and
desirable to carry the PGD pointer in c0_context rather than having to
always load it from memory.

The first patch adds some instructions to uasm that are needed by the
second patch.

The second patch contains the main changes.

I will reply with the two patches.

David Daney (2):
   MIPS: Add drotr and dins instructions to uasm.
   MIPS: Put PGD in C0_CONTEXT for 64-bit R2 processors.

  arch/mips/Kconfig                   |    3 +++
  arch/mips/include/asm/mmu_context.h |   29 ++++++++++++++++++++++++++++-
  arch/mips/include/asm/stackframe.h  |   20 ++++++++++----------
  arch/mips/mm/init.c                 |    2 ++
  arch/mips/mm/tlbex.c                |   28 +++++++++++++++++++++++++---
  arch/mips/mm/uasm.c                 |   16 +++++++++++++---
  arch/mips/mm/uasm.h                 |    7 +++++++
  7 files changed, 88 insertions(+), 17 deletions(-)

             reply	other threads:[~2009-10-14 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 19:15 David Daney [this message]
2009-10-14 19:16 ` [PATCH 1/2] MIPS: Add drotr and dins instructions to uasm David Daney
2009-10-15  9:35   ` Ralf Baechle
2009-10-14 19:16 ` [PATCH 2/2] MIPS: Put PGD in C0_CONTEXT for 64-bit R2 processors David Daney
2009-10-15  9:36   ` Ralf Baechle
2009-10-15 20:05   ` Maciej W. Rozycki
2009-10-15 20:10     ` David Daney
2009-10-15 20:23       ` Maciej W. Rozycki

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=4AD62353.2080603@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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).