From: Ingo Molnar <mingo@elte.hu>
To: Daniel Walker <dwalker@mvista.com>
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: Wed, 29 Nov 2006 08:21:00 +0100 [thread overview]
Message-ID: <20061129072100.GA1983@elte.hu> (raw)
In-Reply-To: <1164751282.7543.25.camel@localhost.localdomain>
* Daniel Walker <dwalker@mvista.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
next prev parent reply other threads:[~2006-11-29 7:24 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
2006-11-29 7:21 ` Ingo Molnar [this message]
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=20061129072100.GA1983@elte.hu \
--to=mingo@elte.hu \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.