From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] improve SMP reschedule and idle routines
Date: Tue, 17 May 2005 08:52:55 +1000 [thread overview]
Message-ID: <42892447.5000304@yahoo.com.au> (raw)
In-Reply-To: <4288A55B.10F7240E@tv-sign.ru>
Oleg Nesterov wrote:
> Nick Piggin wrote:
>
>> void default_idle(void)
>> {
>>+ local_irq_enable();
>>+
>
>
> Stupid question. Why is this sti() needed?
>
> Interrupts are enabled in start_secondary() before cpu_idle()
> call, and they can't be disabled after return from schedule().
>
> The same question applies to poll_idle/mwait_idle.
>
IIRC I tried to do that, but I think I ran into problems with
acpi_processor_idle which looks like it can call the cpu idle
routines with interrupts disabled. I definitely ran into problems
with something.
That should really be cleaned up though (whether we go one way
or the other doesn't matter as much as it being consistent),
I think.
But I wanted to try to keep this patch to a minimum.
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2005-05-16 22:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 13:51 [patch] improve SMP reschedule and idle routines Oleg Nesterov
2005-05-16 22:52 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-27 7:21 Nick Piggin
2005-05-27 8:57 ` Ingo Molnar
2005-05-27 9:11 ` Nick Piggin
2005-05-27 9:20 ` Ingo Molnar
2005-05-27 9:37 ` Nick Piggin
2005-05-27 10:12 ` Ingo Molnar
2005-06-01 6:15 ` Andrew Morton
2005-06-01 6:31 ` Nick Piggin
2005-05-16 4:21 Nick Piggin
2005-05-16 4:21 ` Nick Piggin
[not found] ` <20050515.220455.59467677.davem@davemloft.net>
2005-05-16 5:19 ` Nick Piggin
2005-05-16 5:19 ` Nick Piggin
[not found] ` <20050515.222722.63128129.davem@davemloft.net>
2005-05-16 5:34 ` Nick Piggin
2005-05-16 5:34 ` Nick Piggin
2005-05-17 7:34 ` Nick Piggin
2005-05-17 7:34 ` Nick Piggin
2005-05-17 7:40 ` Ingo Molnar
2005-05-17 7:40 ` Ingo Molnar
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=42892447.5000304@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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.