public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: in_interrupt race
Date: Wed, 24 Apr 2002 14:43:04 +1000	[thread overview]
Message-ID: <E170EcT-0003bW-00@wagner.rustcorp.com.au> (raw)
In-Reply-To: Your message of "Tue, 23 Apr 2002 09:31:51 +0100." <20020423093151.A17302@flint.arm.linux.org.uk>

In message <20020423093151.A17302@flint.arm.linux.org.uk> you write:
> 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?

<sigh>... Of course that should be reversed.
if [ "$CONFIG_SMP" != y ]; then
   bool 'Preemptible Kernel' CONFIG_PREEMPT
fi

Thanks,
Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

  reply	other threads:[~2002-04-24  4:40 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
2002-04-24  4:43             ` Rusty Russell [this message]
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=E170EcT-0003bW-00@wagner.rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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