All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] more robust halt_light
Date: Wed, 03 Mar 2004 21:08:00 +0000	[thread overview]
Message-ID: <1078348080.2480.64.camel@patsy.fc.hp.com> (raw)
In-Reply-To: <1078336640.2480.37.camel@patsy.fc.hp.com>


   I was curious about that myself, but I thought I remembered from
Stephane that the perf counters didn't really recover from a
PAL_HALT_LIGHT on McKinley.  If that's not the case, maybe we can move
the PAL check into perfmon code, and it can selectively disable it as it
needs via the disable_hlt API.  I assume there are some cases were
perfmon wouldn't need to disable halt_light on working PAL, so the rev
check might not go away.

	Alex

On Wed, 2004-03-03 at 13:38, Seth, Rohit wrote:
> The issue with performance counters is only when PAL_HALT_LIGHT is
> enabled.  It is nice to be able to use this power save feature when the
> performance counters are not currently/actively used system wide.  Can
> we use the disable_hlt and enable_hlt APIs (mentioned in the patch
> below) in perfmon kind of tools to disable/enable PAL_HALT_LIGHT
> whenever the system is transitioning in and out of system wide
> performance monitoring.  That way we don't have to have any tests for
> Mckinley, PAL versions etc. etc.
> 
> rohit
> >-----Original Message-----
> >Sent: Wednesday, March 03, 2004 9:57 AM
> >To: linux-ia64@vger.kernel.org
> >Subject: [PATCH] more robust halt_light
> >
> >
> >  This patch adds some i386-ish enable/disable features to the
> >pal_halt_light cpu idle implementation as well as tries to avoid bad
> >interactions with certain revs of PAL on McKinley cpus.  Hopefully this
> >will provide enough flexibility that we can leave it configured on in
> >the kernel by default.  My latest measurements on a 1.3GHz rx2600 show
> >that enabling pal_halt_light in the cpu_idle routine saves 23W/cpu on
> an
> >idle system.
> >
> >   FWIW, I added the enable/disable_hlt routines.  I don't see any
> >consumers of this for ia64 now, but it looked useful.  Patch against
> >latest linux-2.5 bk.  Thanks,
> >
> >	Alex
> >

-- 
Alex Williamson                             HP Linux & Open Source Lab


  parent reply	other threads:[~2004-03-03 21:08 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 [this message]
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
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=1078348080.2480.64.camel@patsy.fc.hp.com \
    --to=alex.williamson@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 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.