Gilles Chanteperdrix wrote:
> Gilles Chanteperdrix wrote:
> > misinterpretation. When issuing syscalls with a fixed muxid whereas
> > there is no interface corresponding to this muxid, the nucleus crashes,
> > but it is acceptable, user-space interfaces should issue an
> > __xn_sys_bind syscall
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
> > Gilles Chanteperdrix wrote:
> > > misinterpretation. When issuing syscalls with a fixed muxid whereas
> > > there is no interface corresponding to this muxid, the nucleus crashes,
> > > but it is acceptable, user-space interfaces should is
[EMAIL PROTECTED] wrote:
> This patch introduces another rttesting driver, xeno_irqbench, for
> measuring external IRQ latencies. The irqbench device is controlled
> by a user-mode tool irqloop. A second tool for plain Linux, irqbench,
> is provided to trigger the event over serial or parallel cros
Hi,
could someone give this scenario a try (requires my recent patch series)
and tell me if you are also seeing excessive latencies:
Start:
irqloop (+xeno_irqbench) -P 99 -t 0
latency -p 200 -P 50
Terminate:
irqloop
The termination seems to cause high latencies to the (then highest-prio)
period
