Date: Thu, 16 Jul 1998 09:04:09 GMT From: jak@cetlink.net (John Kelly) To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG Subject: Re: tickadj -t not changing tick Message-ID: <35afc126.212112276@mail.cetlink.net> In-Reply-To: <199807160853.SAA31913@godzilla.zeta.org.au> References: <199807160853.SAA31913@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 16 Jul 1998 18:53:34 +1000, Bruce Evans <bde@zeta.org.au> wrote: >>>You want to fiddle kern.timecounter.frequency (units: Hz) or >>>kern.timecounter.adjustment (Units: PPM/2^16) >> >>Judging from what Bruce said, it seems that kern.timecounter.frequency >>is derived from the machdep.*_freq variables, so it would be better to >>change them and let the kernel propagate the changes. > >It would be nicest to change the machine-independent variables and let >the kernel propagate the changes to the machine-dependent variables and >hardware. However the kernel makes no attempt to propagate the changes. >OTOH, when you change the m-d variables, the kernel attempts to propagate >the changes, but it doesn't succeed (it sets the active frequency, >possibly causing a glitch due to the non-atomic update, and the change >gets blown away at the next clock interrupt). Argh! So should I change both kern.timecounter.frequency and the machine dependent variable? Will that work? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35afc126.212112276>