From: Robert Love <rml@tech9.net>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Q: preemptible kernel and interrupts consistency.
Date: 11 Jul 2002 14:28:24 -0700 [thread overview]
Message-ID: <1026422904.1244.294.camel@sinai> (raw)
In-Reply-To: <3D2DF64D.838BD6D6@tv-sign.ru>
On Thu, 2002-07-11 at 14:19, Oleg Nesterov wrote:
> Safe? Look, if process does not hold any spinlock and interrupts
> disabled, then any distant implicit call to resched_task() silently
> enables irqs. At least, this must be documented.
If interrupts are disabled, where is this distant implicit call from
resched_task() coming from?
That was my point, aside from interrupt handlers all the
need_resched-touching code is in sched.c and both Ingo and I verified
everything is locked.
If interrupts are disabled, there are no interrupts handlers. And if
you are in an interrupt handler, preemption is already disabled.
Robert Love
next prev parent reply other threads:[~2002-07-11 21:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-11 20:33 Q: preemptible kernel and interrupts consistency Oleg Nesterov
2002-07-11 20:41 ` Robert Love
2002-07-11 21:19 ` Oleg Nesterov
2002-07-11 21:28 ` Robert Love [this message]
2002-07-11 22:07 ` Oleg Nesterov
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=1026422904.1244.294.camel@sinai \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.