From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: ncunningham@cyclades.com, shaohua.li@intel.com, vatsa@in.ibm.com,
Linux-Kernel@vger.kernel.org, spyro@f2s.com,
Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 2.6.14-rc1-git5] sched: disable preempt in idle tasks
Date: Thu, 22 Sep 2005 13:25:57 +1000 [thread overview]
Message-ID: <43322445.6050003@yahoo.com.au> (raw)
In-Reply-To: <20050921183138.52bcdf27.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
Andrew Morton wrote:
> Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>
>>This patch should hopefully fix Nigel's bug.
>>
>> Split out from sched-resched-opt.patch. Tested on i386 with acpi idle
>> and poll idle (previous iterations tested on various other architectures).
>
>
> This makes the emt64 machine reboot itself, which iirc was the behaviour in
> the failing patch from which this one was split out.
>
> The machine is using acpi_processor_idle().
>
OK, thanks. That must be the preempt_disable() being called in
start_secondary(). Maybe I should have listened to the comment.
Can you try the following patch?
--
SUSE Labs, Novell Inc.
[-- Attachment #2: sched-no-preempt-idle-x86-64-fix.patch --]
[-- Type: text/plain, Size: 596 bytes --]
Index: linux-2.6/arch/x86_64/kernel/smpboot.c
===================================================================
--- linux-2.6.orig/arch/x86_64/kernel/smpboot.c 2005-09-22 01:04:03.000000000 +1000
+++ linux-2.6/arch/x86_64/kernel/smpboot.c 2005-09-22 13:24:11.000000000 +1000
@@ -473,8 +473,8 @@ void __cpuinit start_secondary(void)
* booting is too fragile that we want to limit the
* things done here to the most necessary things.
*/
- preempt_disable();
cpu_init();
+ preempt_disable();
smp_callin();
/* otherwise gcc will move up the smp_processor_id before the cpu_init */
next prev parent reply other threads:[~2005-09-22 3:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 15:41 [PATCH 2.6.14-rc1-git5] sched: disable preempt in idle tasks Nick Piggin
2005-09-21 21:43 ` Nigel Cunningham
2005-09-22 1:31 ` Andrew Morton
2005-09-22 3:25 ` Nick Piggin [this message]
2005-09-22 9:03 ` Andi Kleen
2005-09-25 23:24 ` Nigel Cunningham
2005-10-06 23:03 ` Nigel Cunningham
-- strict thread matches above, loose matches on Subject: below --
2005-11-02 2:33 Li, Shaohua
2005-11-02 2:46 ` Nick Piggin
2005-11-02 5:04 ` Nigel Cunningham
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=43322445.6050003@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Linux-Kernel@vger.kernel.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=ncunningham@cyclades.com \
--cc=shaohua.li@intel.com \
--cc=spyro@f2s.com \
--cc=vatsa@in.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox