linux-kernel - Re: 2.6.19-rc6-rt8: alsa xruns

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: <20061129072100.GA1983@elte.hu>
Date:	Wed, 29 Nov 2006 08:21:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Daniel Walker <dwalker@...sta.com>
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


* Daniel Walker <dwalker@...sta.com> wrote:

> > 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.

please talk to John and Thomas about GTOD interfaces. Right now the 
solution used by the latency tracer is working out pretty OK - but if 
something better comes along i can use that too. It's not a burning 
issue though, unless you know of some bug. (i'm not sure what you mean 
by it becoming constrictive)

	Ingo
-
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/