> For some reason, in Jiri's trace we see exit from sys_read with 2, > and then again exit from sys_read with -EAGAIN: > xterm 32028 [000] 43390.908909: syscalls:sys_enter_read: fd: > 0x00000004, buf: 0x02076e8c, count: 0x0 > xterm 32028 [000] 43390.908917: syscalls:sys_exit_read: 0x2 > xterm 32028 [000] 43390.908982: syscalls:sys_exit_read: > 0xfffffffffffffff5 > > I'm not sure how it is possible (either we lost sys_enter, or timestamp > of seconds -EAGAIN is wrong?). I think we might just convert this error > to a warning (we couldn't reproduce it again). > Should I resend the whole series (preferred) or add another patch on > top?
Or probably left it as is, because perf.data is really weird... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
