Jan Kiszka wrote:
Jan Kiszka wrote:
Gilles Chanteperdrix wrote:
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe,
you recently said there is a bug in the x86_64 support when syscall
tracing is enabled. Now I think I stepped on it as well: In order to
validate my APIC
Philippe,
you recently said there is a bug in the x86_64 support when syscall
tracing is enabled. Now I think I stepped on it as well: In order to
validate my APIC frequency patches for that arch, I wanted to use LTTng
there. But as soon as I start the trace, the latency test fails to run,
Jan Kiszka wrote:
Philippe,
you recently said there is a bug in the x86_64 support when syscall
tracing is enabled. Now I think I stepped on it as well: In order to
validate my APIC frequency patches for that arch, I wanted to use LTTng
there. But as soon as I start the trace, the latency
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe,
you recently said there is a bug in the x86_64 support when syscall
tracing is enabled. Now I think I stepped on it as well: In order to
validate my APIC frequency patches for that arch, I wanted to use LTTng
there. But as soon as I start
Philippe Gerum wrote:
Jan Kiszka wrote:
Philippe,
you recently said there is a bug in the x86_64 support when syscall
tracing is enabled. Now I think I stepped on it as well: In order to
validate my APIC frequency patches for that arch, I wanted to use LTTng
there. But as soon