[PATCH 4/9] mm: cris v32 mmu_context_lock

From: Hugh Dickins
Date: Sat Oct 22 2005 - 11:26:08 EST


The cris v32 switch_mm guards get_mmu_context with next->page_table_lock:
good it's not really SMP yet, since get_mmu_context messes with global
variables affecting other mms. Replace by global mmu_context_lock.

Signed-off-by: Hugh Dickins <hugh@xxxxxxxxxxx>
---

arch/cris/arch-v32/mm/tlb.c | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)

--- mm3/arch/cris/arch-v32/mm/tlb.c 2005-10-17 12:05:08.000000000 +0100
+++ mm4/arch/cris/arch-v32/mm/tlb.c 2005-10-22 14:06:42.000000000 +0100
@@ -175,6 +175,8 @@ init_new_context(struct task_struct *tsk
return 0;
}

+static DEFINE_SPINLOCK(mmu_context_lock);
+
/* Called in schedule() just before actually doing the switch_to. */
void
switch_mm(struct mm_struct *prev, struct mm_struct *next,
@@ -183,10 +185,10 @@ switch_mm(struct mm_struct *prev, struct
int cpu = smp_processor_id();

/* Make sure there is a MMU context. */
- spin_lock(&next->page_table_lock);
+ spin_lock(&mmu_context_lock);
get_mmu_context(next);
cpu_set(cpu, next->cpu_vm_mask);
- spin_unlock(&next->page_table_lock);
+ spin_unlock(&mmu_context_lock);

/*
* Remember the pgd for the fault handlers. Keep a seperate copy of it
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/