Commit c3071951 authored by Kumar Gala's avatar Kumar Gala

powerpc/fsl-booke: Add support for tlbilx instructions

The e500mc core supports the new tlbilx instructions that do core
local invalidates and also provide us the ability to take down
all TLB entries matching a given PID.
Signed-off-by: default avatarKumar Gala <galak@kernel.crashing.org>
parent c026c987
...@@ -36,9 +36,9 @@ ...@@ -36,9 +36,9 @@
*/ */
#define MMU_FTR_USE_TLBIVAX_BCAST ASM_CONST(0x00040000) #define MMU_FTR_USE_TLBIVAX_BCAST ASM_CONST(0x00040000)
/* Enable use of tlbilx invalidate-by-PID variant. /* Enable use of tlbilx invalidate instructions.
*/ */
#define MMU_FTR_USE_TLBILX_PID ASM_CONST(0x00080000) #define MMU_FTR_USE_TLBILX ASM_CONST(0x00080000)
/* This indicates that the processor cannot handle multiple outstanding /* This indicates that the processor cannot handle multiple outstanding
* broadcast tlbivax or tlbsync. This makes the code use a spinlock * broadcast tlbivax or tlbsync. This makes the code use a spinlock
......
...@@ -1754,7 +1754,8 @@ static struct cpu_spec __initdata cpu_specs[] = { ...@@ -1754,7 +1754,8 @@ static struct cpu_spec __initdata cpu_specs[] = {
.cpu_name = "e500mc", .cpu_name = "e500mc",
.cpu_features = CPU_FTRS_E500MC, .cpu_features = CPU_FTRS_E500MC,
.cpu_user_features = COMMON_USER_BOOKE | PPC_FEATURE_HAS_FPU, .cpu_user_features = COMMON_USER_BOOKE | PPC_FEATURE_HAS_FPU,
.mmu_features = MMU_FTR_TYPE_FSL_E | MMU_FTR_BIG_PHYS, .mmu_features = MMU_FTR_TYPE_FSL_E | MMU_FTR_BIG_PHYS |
MMU_FTR_USE_TLBILX,
.icache_bsize = 64, .icache_bsize = 64,
.dcache_bsize = 64, .dcache_bsize = 64,
.num_pmcs = 4, .num_pmcs = 4,
......
...@@ -118,25 +118,50 @@ _GLOBAL(_tlbil_pid) ...@@ -118,25 +118,50 @@ _GLOBAL(_tlbil_pid)
#elif defined(CONFIG_FSL_BOOKE) #elif defined(CONFIG_FSL_BOOKE)
/* /*
* FSL BookE implementations. Currently _pid and _all are the * FSL BookE implementations.
* same. This will change when tlbilx is actually supported and *
* performs invalidate-by-PID. This change will be driven by * Since feature sections are using _SECTION_ELSE we need
* mmu_features conditional * to have the larger code path before the _SECTION_ELSE
*/ */
#define MMUCSR0_TLBFI (MMUCSR0_TLB0FI | MMUCSR0_TLB1FI | \
MMUCSR0_TLB2FI | MMUCSR0_TLB3FI)
/* /*
* Flush MMU TLB on the local processor * Flush MMU TLB on the local processor
*/ */
_GLOBAL(_tlbil_pid)
_GLOBAL(_tlbil_all) _GLOBAL(_tlbil_all)
#define MMUCSR0_TLBFI (MMUCSR0_TLB0FI | MMUCSR0_TLB1FI | \ BEGIN_MMU_FTR_SECTION
MMUCSR0_TLB2FI | MMUCSR0_TLB3FI) li r3,(MMUCSR0_TLBFI)@l
mtspr SPRN_MMUCSR0, r3
1:
mfspr r3,SPRN_MMUCSR0
andi. r3,r3,MMUCSR0_TLBFI@l
bne 1b
MMU_FTR_SECTION_ELSE
PPC_TLBILX_ALL(0,0)
ALT_MMU_FTR_SECTION_END_IFCLR(MMU_FTR_USE_TLBILX)
msync
isync
blr
_GLOBAL(_tlbil_pid)
BEGIN_MMU_FTR_SECTION
slwi r3,r3,16
mfmsr r10
wrteei 0
mfspr r4,SPRN_MAS6 /* save MAS6 */
mtspr SPRN_MAS6,r3
PPC_TLBILX_PID(0,0)
mtspr SPRN_MAS6,r4 /* restore MAS6 */
wrtee r10
MMU_FTR_SECTION_ELSE
li r3,(MMUCSR0_TLBFI)@l li r3,(MMUCSR0_TLBFI)@l
mtspr SPRN_MMUCSR0, r3 mtspr SPRN_MMUCSR0, r3
1: 1:
mfspr r3,SPRN_MMUCSR0 mfspr r3,SPRN_MMUCSR0
andi. r3,r3,MMUCSR0_TLBFI@l andi. r3,r3,MMUCSR0_TLBFI@l
bne 1b bne 1b
ALT_MMU_FTR_SECTION_END_IFSET(MMU_FTR_USE_TLBILX)
msync msync
isync isync
blr blr
...@@ -149,7 +174,9 @@ _GLOBAL(_tlbil_va) ...@@ -149,7 +174,9 @@ _GLOBAL(_tlbil_va)
mfmsr r10 mfmsr r10
wrteei 0 wrteei 0
slwi r4,r4,16 slwi r4,r4,16
ori r4,r4,(MAS6_ISIZE(BOOK3E_PAGESZ_4K))@l
mtspr SPRN_MAS6,r4 /* assume AS=0 for now */ mtspr SPRN_MAS6,r4 /* assume AS=0 for now */
BEGIN_MMU_FTR_SECTION
tlbsx 0,r3 tlbsx 0,r3
mfspr r4,SPRN_MAS1 /* check valid */ mfspr r4,SPRN_MAS1 /* check valid */
andis. r3,r4,MAS1_VALID@h andis. r3,r4,MAS1_VALID@h
...@@ -157,6 +184,9 @@ _GLOBAL(_tlbil_va) ...@@ -157,6 +184,9 @@ _GLOBAL(_tlbil_va)
rlwinm r4,r4,0,1,31 rlwinm r4,r4,0,1,31
mtspr SPRN_MAS1,r4 mtspr SPRN_MAS1,r4
tlbwe tlbwe
MMU_FTR_SECTION_ELSE
PPC_TLBILX_VA(0,r3)
ALT_MMU_FTR_SECTION_END_IFCLR(MMU_FTR_USE_TLBILX)
msync msync
isync isync
1: wrtee r10 1: wrtee r10
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment