Date: Thu, 14 Oct 2010 20:59:54 +0100 From: Bruce Cran <bruce@cran.org.uk> To: bf1783@gmail.com Cc: bf1783@googlemail.com, freebsd-questions@freebsd.org Subject: Re: VIA EPIA 5000 and ACPI Cx levels Message-ID: <20101014205954.00000598@unknown> In-Reply-To: <AANLkTi=dHQie0GbC=wj8VAN_aovE4RVey-uJQ%2B1UY0hi@mail.gmail.com> References: <AANLkTimnavr=uZhwSgRnBtNFPuPbQq6Ta4Tvhi8MQ1aS@mail.gmail.com> <201010102228.33095.bruce@cran.org.uk> <AANLkTi=dHQie0GbC=wj8VAN_aovE4RVey-uJQ%2B1UY0hi@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 14 Oct 2010 19:43:36 +0000 "b. f." <bf1783@googlemail.com> wrote: > I'm not sure what is going on here: if you set > hint.attimer.0.timecounter="0" and kern.eventtimer.timer="i8254" in > /boot/loader.conf, then the system should try to use the i8254 in > one-shot mode, unless you've specifically set periodic mode. If > kern.eventtimer.periodic=1, then you are _not_ using one-shot mode. > If it was 0 before your latest changes, then you were previously using > one-shot mode. But, as I wrote earlier, for kern.hz<128 and > kern.eventtimer.singlemul=1, periodic mode may result in more sleeping > than one-shot mode, though at a price. This may be what you are > seeing. Sorry, that was a typo: kern.eventtimer.periodic=0 after setting hint.attimer.0.timecounter=0. I'm seeing 145 interrupts per second now, so setting hz=100 and using singlemul mode would further decrease it - but I guess it's not something you would want to do on a router or desktop. > This or the high latency of C3 may account > for your machine not using it. Also note that you shouldn't use a > LAPIC timer if you are using C3 or deeper sleep states. Thanks. It sounds like things are working as they should then. Good to know the new timer code is working properly on this more unusual hardware! -- Bruce Cran
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20101014205954.00000598>