From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] Documentation update about pal_halt_light
Date: Wed, 09 Mar 2005 18:59:52 +0000 [thread overview]
Message-ID: <16943.18344.12333.503614@napali.hpl.hp.com> (raw)
In-Reply-To: <422F1246.80008@lifl.fr>
>>>>> On Wed, 09 Mar 2005 16:12:06 +0100, Eric Piel <Eric.Piel@lifl.fr> said:
Eric> Hello, I had to hang around in the code to find this
Eric> invaluable option "nohalt". Let's document it!
Eric> That's a trivial documentation update, please apply.
Good catch. I thought it was documented already. Perhaps it got
lost. In any case, I think it would be good to mention why someone
might want to turn it on. Perhaps something along the lines of:
"This increases power-consumption. On the positive side, it
reduces interrupt wake-up latency, which may improve
performance in certain environments such as networked
servers."
--david
Eric> -- Documentation update about pal_halt_light on IA-64
Eric> Signed-off-by: Eric Piel <eric.piel@lifl.fr> -- ---
Eric> kernel-parameters.txt.bak 2005-03-09 15:39:10.348323818 +0100
Eric> +++ kernel-parameters.txt 2005-03-09 15:55:19.583141065 +0100
Eric> @@ -837,6 +837,9 @@ instruction doesn't work correctly and not
Eric> to use it.
Eric> + nohalt [IA-64] Tells the kernel not to use the power saving
Eric> + function PAL_HALT_LIGHT when idle. + noirqdebug [IA-32]
Eric> Disables the code which attempts to detect and disable
Eric> unhandled interrupt sources.
next prev parent reply other threads:[~2005-03-09 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 15:12 [PATCH] Documentation update about pal_halt_light Eric Piel
2005-03-09 18:59 ` David Mosberger [this message]
2005-03-09 23:48 ` Eric Piel
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=16943.18344.12333.503614@napali.hpl.hp.com \
--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