From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-arch@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
David Mosberger <davidm@hpl.hp.com>
Subject: Re: Remaining arch problems in cpu_idle
Date: Thu, 30 Jun 2005 09:38:52 +1000 [thread overview]
Message-ID: <42C3310C.8070004@yahoo.com.au> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F03D0B5D6@scsmsx401.amr.corp.intel.com>
Luck, Tony wrote:
>>h8300, ia64, and sh64 still have possible outstanding issues,
>>which I've put at the end of the Documentation/ file. It
>>would be nice to get these looked at.
>
>
> +ia64 - is safe_halt call racy vs interrupts? (does it sleep?) (See #4a)
>
> safe_halt() makes a call to PAL[1] to go to a lower power state. It does
> not do anything that would require a sleep.
>
So it won't need an interrupt to be revived out of that state?
Thank you Tony, I'll take ia64 off the list.
The other change I made to ia64 is to use TIF_POLLING_NRFLAG to
inhibit wakeup IPIs to idle threads - is this something that
looks acceptable?
Clearing TIF_POLLING_NRFLAG from around safe_halt() in my patch
is superfluous if safe_halt doesn't require an interrupt to wake
up - I'll remove that hunk.
Thanks,
Nick
--
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 23:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 21:51 Remaining arch problems in cpu_idle Luck, Tony
2005-06-29 23:38 ` Nick Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-30 0:07 Luck, Tony
2005-06-30 0:17 ` Nick Piggin
2005-06-29 23:46 Luck, Tony
2005-06-29 23:55 ` Nick Piggin
2005-06-29 7:06 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
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=42C3310C.8070004@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=linux-arch@vger.kernel.org \
--cc=tony.luck@intel.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