From: "Seth, Rohit" <rohit.seth@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] more robust halt_light
Date: Thu, 04 Mar 2004 02:40:41 +0000 [thread overview]
Message-ID: <01EF044AAEE12F4BAAD955CB75064943010F08FF@scsmsx401.sc.intel.com> (raw)
In-Reply-To: <1078336640.2480.37.camel@patsy.fc.hp.com>
>-----Original Message-----
>From: Jesse Barnes [mailto:jbarnes@sgi.com]
>Sent: Wednesday, March 03, 2004 2:56 PM
>To: davidm@hpl.hp.com
>Cc: Alex Williamson; Seth, Rohit; linux-ia64
>Subject: Re: [PATCH] more robust halt_light
>
>On Wed, Mar 03, 2004 at 02:45:11PM -0800, David Mosberger wrote:
>> Can we get rid of the CONFIG option too? Or do folks who care (too?)
>> much about wake-up latency prefer to turn off a CONFIG option over
>> booting with nohlt?
>
>Some people have come to me concerned about the wakeup latency of
having
>the halt call in there, and it also looks like the PAL has a bug on our
>platform that causes hangs when we call PAL_HALT_LIGHT (which we're
>tracking down), so I wouldn't mind if the config option stuck around a
>little longer (or was a boot time parameter at least).
>
>Thanks,
>Jesse
As far as latency is concerned, do you have any specific workload that
is getting impacted (severly) by this transition.
I think we should remove the compile time CONFIG_OPTION for
PAL_HALT_LIGHT. And instead use /proc interface to dynamically
enable/disable the power transition.
next prev parent reply other threads:[~2004-03-04 2:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 17:57 [PATCH] more robust halt_light Alex Williamson
2004-03-03 20:38 ` Seth, Rohit
2004-03-03 21:08 ` Alex Williamson
2004-03-03 22:31 ` Alex Williamson
2004-03-03 22:45 ` David Mosberger
2004-03-03 22:56 ` Jesse Barnes
2004-03-03 23:35 ` Grant Grundler
2004-03-04 2:40 ` Seth, Rohit [this message]
2004-03-04 2:48 ` Seth, Rohit
2004-03-04 15:47 ` Alex Williamson
2004-03-04 17:16 ` Jesse Barnes
2004-03-04 17:17 ` Jesse Barnes
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=01EF044AAEE12F4BAAD955CB75064943010F08FF@scsmsx401.sc.intel.com \
--to=rohit.seth@intel.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