From: Russell King <rmk@arm.linux.org.uk>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: paulus@samba.org, rml@tech9.net, george@mvista.com,
linux-kernel@vger.kernel.org
Subject: Re: in_interrupt race
Date: Tue, 23 Apr 2002 09:31:51 +0100 [thread overview]
Message-ID: <20020423093151.A17302@flint.arm.linux.org.uk> (raw)
In-Reply-To: <15553.17071.88897.914713@argo.ozlabs.ibm.com> <1019502174.939.50.camel@phantasy> <3CC48321.5855B08A@mvista.com> <1019512494.1465.5.camel@phantasy> <15556.38775.439624.762586@argo.ozlabs.ibm.com> <20020423132524.2056739f.rusty@rustcorp.com.au>
On Tue, Apr 23, 2002 at 01:25:24PM +1000, Rusty Russell wrote:
> Yes: the old CPU happens to be processing an interrupt now.
> The neat solution is to follow Linus' original instinct and make
> PREEMPT an option only for UP: I only like preempt because it brings
> UP into line with SMP, effectively enlarging the SMP userbase to reasonable
> size.
> -bool 'Preemptible kernel' CONFIG_PREEMPT
> +dep_bool 'Preemptible kernel' CONFIG_PREEMPT $CONFIG_SMP
> -bool 'Preemptible Kernel' CONFIG_PREEMPT
> +dep_bool 'Preemptible Kernel' CONFIG_PREEMPT $CONFIG_SMP
Do you really mean that CONFIG_PREEMPT is only available if CONFIG_SMP is
'y' or undefined?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-04-23 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 10:27 in_interrupt race Paul Mackerras
2002-04-22 19:02 ` Robert Love
2002-04-22 21:39 ` george anzinger
2002-04-22 21:54 ` Robert Love
2002-04-22 23:06 ` Paul Mackerras
2002-04-22 23:15 ` Robert Love
2002-04-23 3:25 ` Rusty Russell
2002-04-23 8:31 ` Russell King [this message]
2002-04-24 4:43 ` Rusty Russell
2002-04-22 23:22 ` Paul Mackerras
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=20020423093151.A17302@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=rml@tech9.net \
--cc=rusty@rustcorp.com.au \
/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