| 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: <1164751282.7543.25.camel@localhost.localdomain> Date: Tue, 28 Nov 2006 14:01:22 -0800 From: Daniel Walker <dwalker@...sta.com> To: Ingo Molnar <mingo@...e.hu> Cc: Lee Revell <rlrevell@...-job.com>, Fernando Lopez-Lezcano <nando@...ma.Stanford.EDU>, "Linux-Kernel," <linux-kernel@...r.kernel.org> Subject: Re: 2.6.19-rc6-rt8: alsa xruns On Tue, 2006-11-28 at 21:14 +0100, Ingo Molnar wrote: > * Lee Revell <rlrevell@...-job.com> wrote: > > > On Tue, 2006-11-28 at 11:58 -0800, Fernando Lopez-Lezcano wrote: > > > Hi, I'm trying out the latest -rt patch and getting alsa xruns when > > > using jackd and jack clients. This is a sample from the output of > > > qjackctl / jackd (jack 0.102.25, qjackctl 0.2.21): > > > > Any improvement if you disable high res timers? > > > > Also, the latency tracer does not work on dual core AMD machines due > > to the TSC drift. Might as well disable it. > > i fixed this in -rt8: the latency tracer now uses the time of day > clocksource - pmtimer in this case. (that means function tracing is > slower than with the TSC, but latency figures are more reliable.) I have a patch set to make the using the clocksources a little nicer.. Is there anything I should add to that interface to help enable latency tracing, or are you satisfied with using the timekeeping clocksource? It might get constrictive after a while. Daniel - 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