| 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
| ||
|
Date: Sun, 1 Mar 2009 15:44:33 +0000 From: Sitsofe Wheeler <sitsofe@...oo.com> To: Jesper Krogh <jesper@...gh.cc> Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: Linux 2.6.29-rc6 (clocksource) On Sun, Mar 01, 2009 at 04:09:03PM +0100, Jesper Krogh wrote: > Jesper Krogh wrote: > >The "current_clocsource" is the same on both systems. > > > >$ cat /sys/devices/system/clocksource/clocksource0/current_clocksource > >tsc > > What selects the "current_clocksource"? I tried to boot one of the > kernels hat have the problem on another piece of hardware and on that > system it ended up defaulting to "acpi_pm" instead of "tsc". I believe different clock sources have different priorities based on their resolution and behaviour. Clock sources's that "go bad" because hardware interactions are hopefully detected and subsequent "best" clock sources are then tried. There was a nice treatment of different clocksourcs in this kernelnewbies thread: http://www.mail-archive.com/kernelnewbies@nl.linux.org/msg05164.html . -- Sitsofe | http://sucs.org/~sits/ -- 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