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
| ||
|
Message-Id: <1273878957.2825.175.camel@sbs-t61.sc.intel.com> Date: Fri, 14 May 2010 16:15:57 -0700 From: Suresh Siddha <suresh.b.siddha@...el.com> To: john stultz <johnstul@...ibm.com> Cc: Jesper Dangaard Brouer <hawk@...u.dk>, Thomas Gleixner <tglx@...utronix.de>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, netdev <netdev@...r.kernel.org>, "Brown, Len" <len.brown@...el.com>, "Li, Shaohua" <shaohua.li@...el.com>, "hawk@...x.dk" <hawk@...x.dk> Subject: Re: TSC unstable due to TSC halts in idle? On Fri, 2010-05-14 at 15:28 -0700, john stultz wrote: > 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. Jesper mentioned that it is xeon 5550. TSC's for that processor doesn't stop in idle. Perhaps he is using an older kernel which doesn't detect this fact. Jesper, more recent kernels should be able to use TSC as the clocksource. thanks, suresh -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists