From: David Daney <ddaney@caviumnetworks.com>
To: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH 3/3] MIPS: Use C0_KScratch (if present) to hold PGD pointer.
Date: Tue, 21 Dec 2010 10:31:04 -0800 [thread overview]
Message-ID: <4D10F268.8080706@caviumnetworks.com> (raw)
In-Reply-To: <1292879828-20493-4-git-send-email-ddaney@caviumnetworks.com>
On 12/20/2010 01:17 PM, David Daney wrote:
> Decide at runtime to use either Context or KScratch to hold the PGD
> pointer.
>
> Signed-off-by: David Daney<ddaney@caviumnetworks.com>
> ---
> arch/mips/include/asm/mmu_context.h | 8 +--
> arch/mips/kernel/traps.c | 2 +-
> arch/mips/mm/tlbex.c | 110 +++++++++++++++++++++++++++++++---
> 3 files changed, 102 insertions(+), 18 deletions(-)
>
[...]
> /* Install CPU exception handler */
> diff --git a/arch/mips/mm/tlbex.c b/arch/mips/mm/tlbex.c
> index 6184f0a..2e15aa6 100644
> --- a/arch/mips/mm/tlbex.c
> +++ b/arch/mips/mm/tlbex.c
> @@ -26,8 +26,10 @@
> #include<linux/smp.h>
> #include<linux/string.h>
> #include<linux/init.h>
> +#include<linux/cache.h>
>
> -#include<asm/mmu_context.h>
Whoops, that include should stay, it is needed for ip32.
> +#include<asm/cacheflush.h>
> +#include<asm/pgtable.h>
> #include<asm/war.h>
> #include<asm/uasm.h>
>[...]
I will send a revised patch.
prev parent reply other threads:[~2010-12-21 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 21:17 [PATCH 0/3] Allow processors with scratch registers to use them for TLB refill David Daney
2010-12-20 21:17 ` [PATCH 1/3] MIPS: Probe for presence of KScratch registers David Daney
2010-12-20 21:17 ` [PATCH 2/3] MIPS: Add DINSM to uasm David Daney
2010-12-20 21:17 ` [PATCH 3/3] MIPS: Use C0_KScratch (if present) to hold PGD pointer David Daney
2010-12-21 18:31 ` David Daney [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=4D10F268.8080706@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