From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: 2.5.69 process.c: cpu_idle() cleanup
Date: Tue, 13 May 2003 00:48:09 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705745@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705738@msgid-missing>
>>>>> On 12 May 2003 20:41:03 -0400, Jes Sorensen <jes@wildopensource.com> said:
>>>>> "David" = David Mosberger <davidm@napali.hpl.hp.com> writes:
David> Is this a real need or is this just something hypothetical?
David> If the latter, I'd rather leave what's there now.
Jes> The problem with the current code is that it doesn't work for
Jes> generic kernels and for the SN2 we really like to have this
Jes> feature in place. The PROM allows you to go in and look at the
Jes> led status even if the kernel has hung.
Jes> The other reason was that I was trying to get rid of SN
Jes> specific features from generic files and having a more generic
Jes> API for this seemed useful to me.
Jes> So to answer your question, yes I think there is a real use for
Jes> this.
OK, I can probably live with that argument. However, let's make it a
platform vector then (which I was opposed to back when) and make it a
single function (e.g., "mark_idle"), which takes an "idleness"
argument.
--david
next prev parent reply other threads:[~2003-05-13 0:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 23:31 [Linux-ia64] Re: 2.5.69 process.c: cpu_idle() cleanup David Mosberger
2003-05-13 0:41 ` Jes Sorensen
2003-05-13 0:48 ` David Mosberger [this message]
2003-05-13 2:09 ` Jes Sorensen
2003-05-13 6:51 ` David Mosberger
2003-05-13 18:33 ` Jes Sorensen
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=marc-linux-ia64-105590723705745@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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