From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Lee Revell <rlrevell@joe-job.com>,
Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
"Linux-Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc6-rt8: alsa xruns
Date: Tue, 28 Nov 2006 14:01:22 -0800 [thread overview]
Message-ID: <1164751282.7543.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20061128201444.GB26934@elte.hu>
On Tue, 2006-11-28 at 21:14 +0100, Ingo Molnar wrote:
> * Lee Revell <rlrevell@joe-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
next prev parent reply other threads:[~2006-11-28 22:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 19:58 2.6.19-rc6-rt8: alsa xruns Fernando Lopez-Lezcano
2006-11-28 20:09 ` Ingo Molnar
2006-11-28 20:37 ` Fernando Lopez-Lezcano
2006-11-28 21:04 ` Fernando Lopez-Lezcano
2006-11-28 21:35 ` Fernando Lopez-Lezcano
2006-11-28 23:22 ` Fernando Lopez-Lezcano
2006-11-29 7:24 ` Ingo Molnar
2006-11-29 13:43 ` Ingo Molnar
2006-11-29 18:38 ` Fernando Lopez-Lezcano
2006-11-29 19:51 ` Ingo Molnar
2006-11-29 20:22 ` Fernando Lopez-Lezcano
2006-11-29 20:34 ` Fernando Lopez-Lezcano
2006-11-28 20:12 ` Lee Revell
2006-11-28 20:14 ` Ingo Molnar
2006-11-28 22:01 ` Daniel Walker [this message]
2006-11-29 7:21 ` Ingo Molnar
2006-11-29 16:24 ` Daniel Walker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1164751282.7543.25.camel@localhost.localdomain \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nando@ccrma.Stanford.EDU \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox