From: Christian Hildner <christian.hildner@hob.de>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] cpu_halt() question
Date: Tue, 14 Jan 2003 08:34:31 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805669@msgid-missing> (raw)
Hi,
cpu_halt (in process.c) calls ia64_pal_halt_info() every time when it is
called. I assume that cpu_halt is called often and pal_halt_info will
never change for a specific PAL/processor. Why not call
ia64_pal_halt_info() once at setup time and save the min_power_state in
a global variable? This would save power (important when Itanium
notebooks are coming) and (if you are lucky) increases performance if
time needed by the two PAL calls is bigger then the time needed by the
external resource to finish.
Additionally a loop including nops instead of the ia64_pal_halt call
could bring a acceleration of the response of an external interruption
(depending on interrupt handling in PAL).
Opinions?
Christian
next reply other threads:[~2003-01-14 8:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 8:34 Christian Hildner [this message]
2003-01-14 15:36 ` [Linux-ia64] cpu_halt() question Alex Williamson
2003-01-14 22:18 ` Seth, Rohit
2003-01-15 8:47 ` Christian Hildner
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-105590709805669@msgid-missing \
--to=christian.hildner@hob.de \
--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