Date: Tue, 09 Mar 2021 01:50:21 +0900 (JST) From: Yasuhiro Kimura <yasu@utahime.org> To: freebsd-current@freebsd.org Subject: Re: Waiting for bufdaemon Message-ID: <20210309.015021.2131122829257392547.yasu@utahime.org> In-Reply-To: <20210309.005732.1808108188909983665.yasu@utahime.org> References: <CACNAnaEPJftb_1Jg94zpR4AoU5TKEjbXuYcAA0ByUmL0=hPQCg@mail.gmail.com> <YEVpwXGS5UBA8P44@kib.kiev.ua> <20210309.005732.1808108188909983665.yasu@utahime.org>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Yasuhiro Kimura <yasu@utahime.org> Subject: Re: Waiting for bufdaemon Date: Tue, 09 Mar 2021 00:57:32 +0900 (JST) > But still one question remains. Why have the value of > kern.timecounter.hardware and kern.timecounter.tc.ACPI-fast.counter > changed by applying the patch? My understanding is that it only makes > 'kern.timecounter.hardware' loader tunable that can be configured with > loader.conf. Is it unexpected side effect? Or is everything expected > result? Oops, I made a mistake. > If I do it with unpatched kernel, I get following result. This isn't correct. I did it with reverted kernel (i.e. 705d06b289e of main + revert of 84eaf2ccc6a). If I do it with really unpatch kernel, I get same result as patched one. Sorry for noise. --- Yasuhiro Kimura
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20210309.015021.2131122829257392547.yasu>