linux-kernel - Re: TSC unstable due to TSC halts in idle?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <AANLkTimeXEaUnzSBuilbQLHj_oho3ia9EgyPGpB7vJRI@mail.gmail.com>
Date:	Fri, 14 May 2010 15:28:31 -0700
From:	john stultz <johnstul@...ibm.com>
To:	Jesper Dangaard Brouer <hawk@...u.dk>
Cc:	Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
	netdev <netdev@...r.kernel.org>, Len Brown <len.brown@...el.com>,
	Shaohua Li <shaohua.li@...el.com>, hawk@...x.dk
Subject: Re: TSC unstable due to TSC halts in idle?

On Fri, May 14, 2010 at 1:13 PM, Jesper Dangaard Brouer <hawk@...u.dk> wrote:
> I want to know, if its safe to enable the TSC clocksource, when the
> kernel reports:
>  "Marking TSC unstable due to TSC halts in idle"
>
> The system selects HPET (in current_clocksource), but I can still see
> TSC as an available clocksource (in
> /sys/devices/system/clocksource/clocksource0/available_clocksource).
>
> Is it safe to enable TSC manually (by changing current_clocksource)?
> (my workload is 10Git/s routing, cannot survive with a slow clock)
>
>
> Any trick to avoid this? (e.g. kernel config setting, or a /sys/ setting
> which changes the minimum P-state?)

Might try booting with the max-cstate=1 option.

thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/