Date: Thu, 23 Feb 2017 12:08:29 +0200 From: Konstantin Belousov <kostikbel@gmail.com> To: Jia-Shiun Li <jiashiun@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org>, John Baldwin <jhb@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Subject: Re: TSC as timecounter makes system lag Message-ID: <20170223100829.GR2092@kib.kiev.ua> In-Reply-To: <CAHNYxxN7xF3S71E%2BZpvzKNiMr%2B2F9hov6v2Yq_dqm1aAbZt3xw@mail.gmail.com> References: <20170113120534.GC2349@kib.kiev.ua> <CAHNYxxNN3p4KGvAnQ0aYUFmucGBKKj4JWgATNYZS2n0WTMY78g@mail.gmail.com> <20170115202008.GL2349@kib.kiev.ua> <CAHNYxxNxJp6jVmS0petqMmhdMe0Bam%2BtgUzufFVYWnSSxeGxoA@mail.gmail.com> <20170116120021.GQ2349@kib.kiev.ua> <CAHNYxxO7jeMFCkzQy-J2odu1yZS2UMO36kS58AQAUkXAHqVCPg@mail.gmail.com> <5f814a7a-5e46-057e-62ad-dde0a61bc1c8@selasky.org> <CAHNYxxOJ=dgX5%2Bu%2BSCaE%2Bhv0TXWLfijeh6cnOuK68Fu%2BZRO39A@mail.gmail.com> <CAHNYxxMfeAyQXuMaS8auQc_mHtK%2Bun7ZHZe7EbdFSzXJkUt=hQ@mail.gmail.com> <CAHNYxxN7xF3S71E%2BZpvzKNiMr%2B2F9hov6v2Yq_dqm1aAbZt3xw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 23, 2017 at 01:11:29AM +0800, Jia-Shiun Li wrote:
> I got the impression that TSC was not preferred timecounter
> if it is not C-state invariant. But this apparenly is not the case now.
> Dig a bit and found r277900 chose to prefer TSC over saving power
> by disabling C2 state when TSC is selected as timecounter.
>
> But with EARLY_AP_STARTUP, and TSC as timecounter,
> CPU still enters C2 state.
> (Observed by sysctl dev.cpu.0.cx_usage_counters)
> With nooptions EARLY_AP_STARTUP, CPU correctly stays 100%
> in C1 and no lower.
>
> I added a printf in tc_windup() to check. With EARLY_AP_STARTUP,
> cpu_disable_c2_sleep is never increased, so it can not prevent CPU
> from entering C2.
>
> Guess there's some kind of race or init order issue, but it is
> beyond my understanding for now.
This is a useful analysis.
Yes, I think that there is an init ordering issue. Note that
cpu_disable_c2_sleep is only changed in tc_windup() when timecounter
is changed. If existing and already engadged timecounter suddenly gets
TC_FLAG_C2STOP set, tc_windup() ignores the flag. And with the early
AP startup, tsc seems to be set as timecounter too early.
Just moving order of init_TSC_tc() would not help, since tsc checks smp
consistency, which requires started APs. Try this for now, but might
be John has better idea how to handle the issue. You might need to add
some extern declarations for the patch to compile.
diff --git a/sys/x86/x86/tsc.c b/sys/x86/x86/tsc.c
index 3f36fbd9f8a..f8e33069c70 100644
--- a/sys/x86/x86/tsc.c
+++ b/sys/x86/x86/tsc.c
@@ -545,6 +545,8 @@ init_TSC_tc(void)
if (cpu_deepest_sleep >= 2 && cpu_vendor_id == CPU_VENDOR_INTEL &&
(amd_pminfo & AMDPM_TSC_INVARIANT) == 0) {
tsc_timecounter.tc_flags |= TC_FLAGS_C2STOP;
+ if (timecounter == &tsc_timecounter)
+ cpu_disable_c2_sleep++;
if (bootverbose)
printf("TSC timecounter disables C2 and C3.\n");
}
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170223100829.GR2092>