[lkml]   [2005]   [Sep]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Jackit-devel] Re: jack, PREEMPT_DESKTOP, delayed interrupts?

* Florian Schmidt <> wrote:

> > JACK sources already include a CHECK_PREEMPTION() macro which expands
> > to Ingo's special gettimeofday() calls. The trace is turned on and
> > then off automatically before and after the realtime critical section
> > in the process thread (see libjack/client.c).
> Just for completeness sake:
> you need to build jackd with --enable-preemption-check

this is another feature, unrelated to latency tracing. So (an adapted
version of) the latency-tracing patch i sent should still be tried.

--enable-preemption-check does the 'send SIGUSR2 if jackd gets scheduled
unexpectedly'. That might unearth latencies, but it does not by itself
measure latencies. Right now we are more interested in the latencies

i suspect the confusion comes from the API hacks i'm using: user-space
tracing is started/stopped via:


while 'jackd does not want to be scheduled' flag is switched on/off via:


(introducing extra syscalls for this is an overkill.)

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-09-01 09:34    [W:0.046 / U:0.476 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site