public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Duraid Madina <duraid@octopus.com.au>
To: linux-ia64@vger.kernel.org
Subject: pal/power_info for real?
Date: Tue, 25 Nov 2003 09:09:31 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106975147501700@msgid-missing> (raw)

Hi all,

	/proc/pal/cpu0/power_info on my system reads:

Power level 0:
         entry_latency       : 9000 cycles
         exit_latency        : 8700 cycles
         power consumption   : 52000 mW
         Cache+TLB coherency : Yes
Power level 1: not implemented
Power level 2:
         entry_latency       : 14000 cycles
         exit_latency        : 8700 cycles
         power consumption   : 52000 mW
         Cache+TLB coherency : Yes
Power level 3: not implemented
Power level 4: not implemented
Power level 5: not implemented
Power level 6: not implemented
Power level 7: not implemented


	Is this correct? Two power levels, with different entry latencies, but 
the same power consumption?

	Bracing myself for a particularly warm summer,

	Duraid


             reply	other threads:[~2003-11-25  9:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-25  9:09 Duraid Madina [this message]
2003-11-25 18:24 ` pal/power_info for real? Alex Williamson

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-106975147501700@msgid-missing \
    --to=duraid@octopus.com.au \
    --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