From: Scott Wood <scottwood@freescale.com>
To: root <christophe.leroy@c-s.fr>
Cc: linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 0/5] powerpc8xx: Further optimisation of TLB handling
Date: Fri, 17 Apr 2015 12:25:34 -0500 [thread overview]
Message-ID: <1429291534.4352.2.camel@freescale.com> (raw)
In-Reply-To: <cover.1429287688.git.christophe.leroy@c-s.fr>
On Fri, 2015-04-17 at 18:32 +0200, root wrote:
> This patchset provides a further optimisation of TLB handling in the 8xx.
> Changes are:
> - Not saving registers like CR when not needed
> - Adding support to any TASK_SIZE
>
> Only the last patch of the set is changed compared to v4
>
> Christophe Leroy (5):
> powerpc/8xx: macro for handling CPU15 errata
> powerpc/8xx: Handle CR out of exception PROLOG/EPILOG
> powerpc/8xx: dont save CR in SCRATCH registers
> powerpc/8xx: Use SPRG2 instead of DAR for saving r3
> powerpc/8xx: Add support for TASK_SIZE greater than 0x80000000
>
> arch/powerpc/kernel/head_8xx.S | 79 +++++++++++++++++++++++++++---------------
> 1 file changed, 51 insertions(+), 28 deletions(-)
>
Do you really want your name in the git history to be "root"?
-Scott
prev parent reply other threads:[~2015-04-17 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 16:32 [PATCH v5 0/5] powerpc8xx: Further optimisation of TLB handling root
2015-04-17 16:32 ` [PATCH v5 1/5] powerpc/8xx: macro for handling CPU15 errata root
2015-04-17 16:32 ` [PATCH v5 2/5] powerpc/8xx: Handle CR out of exception PROLOG/EPILOG root
2015-04-17 16:32 ` [PATCH v5 3/5] powerpc/8xx: dont save CR in SCRATCH registers root
2015-04-17 16:32 ` [PATCH v5 4/5] powerpc/8xx: Use SPRG2 instead of DAR for saving r3 root
2015-04-17 16:33 ` [PATCH v5 5/5] powerpc/8xx: Add support for TASK_SIZE greater than 0x80000000 root
2015-04-17 17:25 ` Scott Wood [this message]
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=1429291534.4352.2.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).