From: Robert Love <rml@tech9.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] misc. kernel preemption bits
Date: 29 Aug 2002 14:39:25 -0400 [thread overview]
Message-ID: <1030646366.979.2573.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.44.0208291136180.2316-100000@home.transmeta.com>
On Thu, 2002-08-29 at 14:38, Linus Torvalds wrote:
> I think we should return silently, and simply consider the case of
> disabled local interrupts to be equivalent to having preemption disabled.
>
> So I would remove even the warning.
>
> Comments?
This is a tough question.
I originally did just that but Ingo said we should aim to find the
problem areas, too. The issue is, for 99% of the cases, disabling
interrupts really is equivalent to disabling preemption (e.g.
preempt_schedule() is never called). For the remaining 1% of the cases,
it is possible to fix up the problems by playing safely with interrupts
off.
We _must_ return since we are seeing these in the wild. If we want to
leave the debug checking to try to "fix" the remaining cases we can do
so too.
How about this: add the return now (i.e. accept the patch as-is) and
keep the debug check so we can continue to find areas that cause
incorrect preemptions. Before 2.6, I will send a patch to remove the
check and just return silently.
Sound good?
Robert Love
prev parent reply other threads:[~2002-08-29 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-29 15:33 [PATCH] misc. kernel preemption bits Robert Love
2002-08-29 18:24 ` Andrew Morton
2002-08-29 19:11 ` Robert Love
2002-08-29 21:07 ` george anzinger
2002-08-29 18:38 ` Linus Torvalds
2002-08-29 18:39 ` Robert Love [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=1030646366.979.2573.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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 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.