From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Paul Mundt <lethal@linux-sh.org>
Cc: linux-arch@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Remaining arch problems in cpu_idle
Date: Wed, 29 Jun 2005 20:20:43 +1000 [thread overview]
Message-ID: <42C275FB.40209@yahoo.com.au> (raw)
In-Reply-To: <20050629101145.GB2694@linux-sh.org>
Paul Mundt wrote:
> On Wed, Jun 29, 2005 at 07:09:38PM +1000, Nick Piggin wrote:
>>Now this might introduce some power and heat penalty. What's more,
>>your race isn't a fatal one: in the worst case, it should just
>>stall until the next timer interrupt (aside, that might be fatal
>>with a tickless kernel).
>>
>
> After incorporating your changes, how about this?
>
So, just ignore the race, remove the irq disabling completely?
(with the hlt_counter fallback for busy waiting). If you're
happy with that then I think it looks good. Thanks Paul.
I'll also update the Documentation/ file to point out that such
a race isn't fatal.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-06-29 10:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 7:06 Remaining arch problems in cpu_idle Nick Piggin
2005-06-29 8:00 ` Paul Mundt
2005-06-29 9:09 ` Nick Piggin
2005-06-29 10:11 ` Paul Mundt
2005-06-29 10:20 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-29 21:51 Luck, Tony
2005-06-29 23:38 ` Nick Piggin
2005-06-29 23:46 Luck, Tony
2005-06-29 23:55 ` Nick Piggin
2005-06-30 0:07 Luck, Tony
2005-06-30 0:17 ` Nick Piggin
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=42C275FB.40209@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
/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.