Ingo Molnar <[EMAIL PROTECTED]> writes:
> i suspect the confusion comes from the API hacks i'm using: user-space
> tracing is started/stopped via:
>
> gettimeofday(0,1);
> gettimeofday(0,0);
>
> while 'jackd does not want to be scheduled' flag is switched on/off via:
>
> gettime
* Florian Schmidt <[EMAIL PROTECTED]> 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 l
On Wed, 31 Aug 2005 07:08:08 -0500
"Jack O'Quin" <[EMAIL PROTECTED]> 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
Ingo Molnar <[EMAIL PROTECTED]> writes:
> - if everything fails and automatic latency tracing does not show
> anything out of ordinary, then you could try to do "user-triggered
> tracing" of jackd's critical path. This is more laborous to do, but
> should pinpoint the latency reason in a p
4 matches
Mail list logo
