From: Justin Carlson <justin@cs.cmu.edu>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Atomicity & preemptive kernels
Date: 11 Jun 2002 12:56:59 -0700 [thread overview]
Message-ID: <1023825419.2776.13.camel@localhost.localdomain> (raw)
In-Reply-To: <3D0644F4.8070902@mvista.com>
On Tue, 2002-06-11 at 11:44, Jun Sun wrote:
> I see your point now.
>
> However, the race is not there. switch_mm() is only called from inside
> schedule() function, which as a whole is preemption-safe. In other words, the
> above event sequence won't cause a context switch until we exit from
> schedule() function.
>
Yes, but the initial code I cited was explicitly not in the schedule
function. It was an icache_flush_page() implementation.
Just something to be careful of. I think it's going to bite more than a
few people as a bug that's about impossible to track down...
-Justin
prev parent reply other threads:[~2002-06-11 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 19:44 Atomicity & preemptive kernels Justin Carlson
2002-06-10 22:14 ` Jun Sun
2002-06-11 0:00 ` Justin Carlson
2002-06-11 18:44 ` Jun Sun
2002-06-11 19:56 ` Justin Carlson [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=1023825419.2776.13.camel@localhost.localdomain \
--to=justin@cs.cmu.edu \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
/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