Happy to see that in the latest SLES9 kernel, the hz_timer is now
off by default. It was so easy to miss that setting.
Rob
--
Rob van der Heij
Velocity Software, Inc
http://velocitysoftware.com/
--
For LINUX-390 subscribe
Happy to see that in the latest SLES9 kernel, the hz_timer is now
off by default. It was so easy to miss that setting.
Thanks, because I had forgotten on my last 7 guests.
Mark D Pace
Senior Systems Engineer
Mainline Information Systems
1700 Summit Lake Drive
Tallahassee, FL. 32317
Office
I am trying to set my SLES8 guest up to have hz_timer set to 0 at boot. I
have found that this can be done using sysctl.conf or dynamically by
sysctl kernel.hz_timer=0. However, it seems that the sysctl
kernel.hz_timer=0 command does not work.
See the following:
sysctl kernel.hz_timer
Issue the command 'sysctl -p' after boot ( /etc/rc.d/boot.local).
On Thu, 2004-02-05 at 14:04, Eric Sammons wrote:
I am trying to set my SLES8 guest up to have hz_timer set to 0 at boot. I
have found that this can be done using sysctl.conf or dynamically by
sysctl kernel.hz_timer=0. However
: [LINUX-390] Problem with sysctl and hz_timer on SLES8
I am trying to set my SLES8 guest up to have hz_timer set to 0 at boot. I
have found that this can be done using sysctl.conf or dynamically by
sysctl kernel.hz_timer=0. However, it seems that the sysctl
kernel.hz_timer=0 command does not work
Alan Cox wrote:
For an x86 hypervisor you'd probably use the APM interface to do this.
On modern x86 hlt also doesn't save power.
I looked into the APM stuff in Linux for a generic way to let Linux
tell VM it does not need resources allocated now, but did not like
what I saw. From what I can tell
On Fri, 2003-06-13 at 02:03, John Summerfield wrote:
I would have thought it better to look at ACPI, which is supposed to
replace APM.
FWIW, all ACPI has ever done for me, on either my Thinkpad X20 or my
white-box dual-proc P3/866, is to generate kernel panics and keep me
from booting.
Adam
On Fri, 13 Jun 2003, Adam Thornton wrote:
On Fri, 2003-06-13 at 02:03, John Summerfield wrote:
I would have thought it better to look at ACPI, which is supposed to
replace APM.
FWIW, all ACPI has ever done for me, on either my Thinkpad X20 or my
white-box dual-proc P3/866, is to generate
On Thu, 12 Jun 2003, John Summerfield wrote:
On Wed, 11 Jun 2003, Rod Furey wrote:
A more interesting question is: what do the User Mode Linux patches
do?
Run real, unmodified* Linux programs in a virtual computer. UML uses
standard user-space API to access virtual devices and memory.
On Thu, Jun 12, 2003 at 10:24:08PM +1200, Vic Cross wrote:
On Thu, 12 Jun 2003, John Summerfield wrote:
On Wed, 11 Jun 2003, Rod Furey wrote:
A more interesting question is: what do the User Mode Linux patches
do?
Run real, unmodified* Linux programs in a virtual computer. UML
This is a kernel compile-time option.
make menuconfig ---
General setup ---
[*] No HZ timer ticks in idle
[*] Idle HZ timer on by default
Erm... does it let you try this trick with any type
of processor? Could I build this into a PowerPC
nucleus for
The option doesn't show up in my Intel .config file. I would have to say
that this particular option is Linux/390 specific.
Mark Post
-Original Message-
From: Rod Furey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 7:27 AM
To: [EMAIL PROTECTED]
Subject: Re: hz_timer
John wrote:
Did you try the man command?
Surprise, surprise!
Regards, Jim
Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs
t/l 543-4021, 408-463-4021, [EMAIL PROTECTED]
*** Grace Happens ***
hypervisor, so the timer patch probably would not help.
-Original Message-
From: Rod Furey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 4:27 AM
To: [EMAIL PROTECTED]
Subject: Re: hz_timer
This is a kernel compile-time option.
make menuconfig ---
General setup
On Mer, 2003-06-11 at 18:13, Fargusson.Alan wrote:
Part of the timer patch is machine dependant. Since most systems that run Linux
don't have anything like VM there isn't any point in implementing the timer patch on
them.
I suspect that the (misnamed) halt instruction on the Intel system
action based on it, is
strictly prohibited.
-Original Message-
From: Fargusson.Alan [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 11, 2003 12:33 PM
To: [EMAIL PROTECTED]
Subject: Re: hz_timer
Interesting idea. Something similar would probably apply to
other processors as well
What about somebody running Linux/Intel under Windows using VMWare? Or
somebody (weird?) running multiple Linux/Intel servers under VMWare/ESX?
A more interesting question is: what do the User Mode Linux patches
do?
(Not being up on the internals of the kernel and not being able
to read the stuff
On Wed, 11 Jun 2003, Rod Furey wrote:
What about somebody running Linux/Intel under Windows using VMWare? Or
somebody (weird?) running multiple Linux/Intel servers under VMWare/ESX?
A more interesting question is: what do the User Mode Linux patches
do?
Run real, unmodified* Linux
When I do a
cat /proc/sys/kernel/hz_timer
it shows a '1'.
I set it to '0' as suggested for VM types. But after a boot, it is back
to '1'. The documentation on this doesn't say anything about needing to
put it in a boot script. Seems to imply that this is a one time only
thing.
So..
1. Am I
On Tue, 2003-06-10 at 12:31, Tom Duerbusch wrote:
When I do a
cat /proc/sys/kernel/hz_timer
it shows a '1'.
I set it to '0' as suggested for VM types. But after a boot, it is back
to '1'. The documentation on this doesn't say anything about needing to
put it in a boot script. Seems
:32 PM
To: [EMAIL PROTECTED]
Subject: hz_timer
When I do a
cat /proc/sys/kernel/hz_timer
it shows a '1'.
I set it to '0' as suggested for VM types. But after a boot, it is back
to '1'. The documentation on this doesn't say anything about needing to
put it in a boot script. Seems to imply
Does SuSE have an /etc/sysctl.conf?
If so, try putting a kernel.hz_timer = 0 in it... sysctl.conf's purpose
is to hold desired values for runtime-adjustable kernel parameters (like
at boot time), and you'd probably be better served placing your values
here than needing to hunt around for it at
On Tue, 10 Jun 2003, Tom Duerbusch wrote:
I set it to '0' as suggested for VM types. But after a boot, it is back
to '1'. The documentation on this doesn't say anything about needing to
put it in a boot script. Seems to imply that this is a one time only
thing.
...
3. Is the docs wrong
For those of us that have to build for both LPAR and VM, you might consider
adding this code to /etc/init.d/boot.local
if [ $(grep -c version = FF /proc/cpuinfo) != 0 ]
then
/sbin/sysctl -w kernel.hz_timer=0
fi
Regards, Jim
Linux S/390-zSeries Support, SEEL, IBM
On Tue, 10 Jun 2003, Tom Duerbusch wrote:
When I do a
cat /proc/sys/kernel/hz_timer
it shows a '1'.
I set it to '0' as suggested for VM types. But after a boot, it is back
to '1'. The documentation on this doesn't say anything about needing to
Of course
put it in a boot script. Seems
So where is /etc/sysctl.conf documented? I did a grep on the string in the
/usr/src/linux directory and and I found some informaiton on sysctl, bit I
did not find the file (though I did a developer's opinion that one should
read the code to find out how sysctl works!.
So where does one look to
On Tue, 10 Jun 2003, Jim Sibley wrote:
So where is /etc/sysctl.conf documented? I did a grep on the string in the
/usr/src/linux directory and and I found some informaiton on sysctl, bit I
did not find the file (though I did a developer's opinion that one should
read the code to find out how
27 matches
Mail list logo
