| 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: <498C78C9.5090405@candelatech.com> Date: Fri, 06 Feb 2009 09:52:09 -0800 From: Ben Greear <greearb@...delatech.com> To: Jiri Kosina <jkosina@...e.cz> CC: linux-kernel <linux-kernel@...r.kernel.org>, rusty@...tcorp.com.au Subject: Re: PATCH: Allow user to force 'tsc' to be treated as stable. Jiri Kosina wrote: > On Thu, 5 Feb 2009, Ben Greear wrote: > >> Allow user to force TSC as stable clock-source. Works around BIOS issues >> in the FWA-7304 (Via CN700 chipset) system, and possibly others. > > How do you know that the TSC is stable on such system? What was the reason > for kernel marking it unstable? I've used it for a timing source in my own modules and it has worked well. It could still be broken in some way, but if so, I'm not sure how to detect it. Ingo sent me a program to test the tsc, and at least for short runs, it showed no problem. Another person suggested the system might think it is unstable because I have ACPI disabled in my BIOS and that might cause the kernel not to have a 'PM timer' that it uses to check the tsc? Other than that, I have no idea why the kernel thinks the tsc is unstable. Thanks, Ben -- Ben Greear <greearb@...delatech.com> Candela Technologies Inc http://www.candelatech.com -- 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/
Powered by blists - more mailing lists