From: Jon Masters <jonathan@jonmasters.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: pm_idle generic register/unregister
Date: Tue, 11 Mar 2008 03:02:34 -0400 [thread overview]
Message-ID: <1205218954.27299.91.camel@perihelion> (raw)
Yo,
I'm working on a patch (needed for the Real Time tree) to cleanup use of
the pm_idle pointer, something each architecture defines and optionally
calls from within the CPU idle loop, if it's defined. The problem is
that there's a classical bug (which has existed for quite some time)
whenever a function providing that pointer is unloaded from under it.
So, I'm proposing an ordered list of pm_idle functions with a
register/unregister function to ensure safe access. Anyway, before I
post that, does anyone have a good reason for why things are as they are
currently in the kernel with respect to the pm_idle stuff? Cruftiness?
Jon.
reply other threads:[~2008-03-11 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1205218954.27299.91.camel@perihelion \
--to=jonathan@jonmasters.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox