From: Kumar Gala <kumar.gala@freescale.com>
To: "Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Cc: "Linux Kernel list" <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@osdl.org>, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: Problem with cpu_rest() change
Date: Tue, 25 Jan 2005 23:45:33 -0600 [thread overview]
Message-ID: <7E912176-6F5D-11D9-986F-000393DBC2E8@freescale.com> (raw)
In-Reply-To: <1106696952.6244.22.camel@gaston>
Will these changes cause us to back out the patch already made to
arch/ppc/kernel/idle.c for systems that did not support powersavings?
- kumar
On Jan 25, 2005, at 5:49 PM, Benjamin Herrenschmidt wrote:
> On Tue, 2005-01-25 at 10:01 +0100, Ingo Molnar wrote:
>
> > it can be bad for the idle task to hold the BKL and to have
> preemption
> > enabled - in such a situation the scheduler will get confused if an
> > interrupt triggers a forced preemption in that small window. But
> it's
> > not necessary to keep IRQs disabled after the BKL has been dropped.
> In
> > fact i think IRQ-disabling doesnt have to be done at all, the patch
> > below ought to solve this scenario equally well, and should solve
> the
> > PPC side-effects too.
> >
> > Tested ontop of 2.6.11-rc2 on x86 PREEMPT+SMP and PREEMPT+!SMP (which
> > IIRC were the config variants that triggered the original problem),
> on
> > an SMP and on a UP system.
>
> Excellent, thanks.
>
> Ben.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2005-01-26 5:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 2:40 Problem with cpu_rest() change Benjamin Herrenschmidt
2005-01-25 9:01 ` Ingo Molnar
2005-01-25 23:49 ` Benjamin Herrenschmidt
2005-01-26 5:45 ` Kumar Gala [this message]
2005-01-26 13:44 ` Benjamin Herrenschmidt
2005-01-26 14:10 ` Kumar Gala
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=7E912176-6F5D-11D9-986F-000393DBC2E8@freescale.com \
--to=kumar.gala@freescale.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.