From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <adf30368253013c874236cf40a6b9ac4@plan9.bell-labs.com>
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] odd clock behaviour
In-Reply-To: <ea2be667cbc9e962ffbee58fd0bb02bf@vitanuova.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu, 13 Mar 2003 14:15:30 -0500
Topicbox-Message-UUID: 7fc9fe34-eacb-11e9-9e20-41e7f4b1d025

Try setting the variable i8253dotimerset to 0 (it's now set to 1).
	echo off > '#P'/i8253timerset
This will keep timerintr() from constantly
changing the period.  I'm always afraid that changing the 8253
on the fly will break something since it's not done much by
other systems and therefore not really well tested.

As long as edf isn't being used (which I think is true everywhere)
it won't hurt to do that.  I think that rsc does it for vmware
to avoid slow downs due to the constant clock trimming.