From: Juan Quintela <quintela@mandrakesoft.com>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [RFC & PATCH] fixing tlb flush race problem on smp
Date: Wed, 22 Jan 2003 08:43:26 +0100 [thread overview]
Message-ID: <86bs297hpd.fsf@trasno.mitica> (raw)
In-Reply-To: <20030121143726.C16939@mvista.com> (Jun Sun's message of "Tue, 21 Jan 2003 14:37:26 -0800")
>>>>> "jun" == Jun Sun <jsun@mvista.com> writes:
Hi
just nickpitting.
jun> + } else {
jun> + /* drop the current context completely */
jun> + CPU_CONTEXT(cpu, mm) = 0;
jun> }
jun> }
jun> __restore_flags(flags);
Perhaps creating a inline function for this, as the code is identical
in both branches?
jun> diff -Nru link/include/asm-mips/mmu_context.h.orig link/include/asm-mips/mmu_context.h
jun> --- link/include/asm-mips/mmu_context.h.orig Tue Jan 21 13:55:43 2003
jun> +++ link/include/asm-mips/mmu_context.h Tue Jan 21 14:01:19 2003
jun> @@ -89,12 +89,25 @@
jun> static inline void switch_mm(struct mm_struct *prev, struct mm_struct *next,
jun> struct task_struct *tsk, unsigned cpu)
jun> {
jun> + unsigned long flags;
jun> +
jun> + __save_and_cli(flags);
s/__save_and_cli()/local_irq_save()/
jun> + __restore_flags(flags);
s/__restore_flags()/local_irq_restore()/
Same in the other occurence, please.
Later, Juan.
--
In theory, practice and theory are the same, but in practice they
are different -- Larry McVoy
next prev parent reply other threads:[~2003-01-22 7:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-21 22:37 [RFC & PATCH] fixing tlb flush race problem on smp Jun Sun
2003-01-22 7:43 ` Juan Quintela [this message]
2003-01-28 1:03 ` Jun Sun
2003-01-29 8:06 ` Ralf Baechle
2003-02-05 0:02 ` Jun Sun
2003-02-05 0:02 ` Jun Sun
2003-02-14 4:48 ` Atsushi Nemoto
2003-02-14 11:06 ` Maciej W. Rozycki
2003-01-29 7:28 ` Ralf Baechle
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=86bs297hpd.fsf@trasno.mitica \
--to=quintela@mandrakesoft.com \
--cc=jsun@mvista.com \
--cc=linux-mips@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