Feature #20
closedFinish x86 syscalls
Added by Anonymous almost 13 years ago. Updated almost 12 years ago.
50%
Description
Implement all system calls on x86-32 and x86-64. A couple of them were still "sys_unknown".
Updated by Anonymous almost 13 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
Not sure what the exact status is on this one.
(We'll get to test how In Progess shows up in the roadmap ;) )
Updated by Mathieu Desnoyers almost 13 years ago
unknown x86-64 syscalls:
1) #define __NR_clone 56
[13:41:22.435972637] (+0.000003118) sys_unknown: { 2 }, { id = 56, args = [ [0] = 1041, [1] = 140683967913968, [2] = 0, [3] = 4237664, [4] = 0, [5] = 0 ] }
2) #define __NR_sync_file_range 277
[13:41:22.437174806] (+0.000005610) sys_unknown: { 1 }, { id = 277, args = [ [0] = 24, [1] = 0, [2] = 4096, [3] = 2, [4] = 4096, [5] = 5 ] }
3) #define __NR_fadvise64 221
[13:41:22.438536916] (+0.000006846) sys_unknown: { 1 }, { id = 221, args = [ [0] = 24, [1] = 0, [2] = 4096, [3] = 4, [4] = 4096, [5] = 5 ] }
4) #define __NR_rt_sigreturn 15
[13:41:22.569928223] (+0.000000948) sys_unknown: { 2 }, { id = 15, args = [ [0] = 17, [1] = 140733276957084, [2] = 1, [3] = 1, [4] = 0, [5] = 72340172838076673 ] }
5) #define __NR_arch_prctl 158
[13:41:22.571722347] (+0.000002105) sys_unknown: { 5 }, { id = 158, args = [ [0]
= 4098, [1] = 140446205236992, [2] = 140446205231104, [3] = 34, [4] =
4294967295, [5] = 0 ] }
6) #define __NR_getcpu 309
[13:41:24.514576205] (+0.000002468) sys_unknown: { 7 }, { id = 309, args = [ [0] = 140736468064656, [1] = 0, [2] = 140665424136152, [3] = 9, [4] = 39694496, [5] = 1 ] }
Updated by Mathieu Desnoyers almost 13 years ago
commit ba21566bd4d49e97184ac34bec82a95f47da28b4
Author: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Date: Wed Feb 15 21:48:30 2012 -0500
Add sys_clone x86 instrumentationSigned-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>Updated by Mathieu Desnoyers almost 13 years ago
commit b5aa4b6a4efc476e3a9b9fafcafd080d9aaa173e
Author: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Date: Wed Feb 15 22:13:43 2012 -0500
syscall tracing: sys_getcpuSigned-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>Updated by Mathieu Desnoyers almost 13 years ago
- Priority changed from Normal to Low
- Target version changed from 2.0 RC1 to 2.1 pre
Updated by Mathieu Desnoyers almost 13 years ago
- Assignee deleted (
Mathieu Desnoyers)
Updated by Anonymous almost 13 years ago
- Status changed from In Progress to Resolved
Updated by Mathieu Desnoyers almost 12 years ago
For those trying to make sense out of the sys_unknown events, the "id" field indicates the system call number. System calls for which probes are not yet implemented within LTTng 2.x appear as "sys_unknown".
The mapping between system call ID and its actual name can be done manually by looking at your architecture-specific unistd.h file, usually installed system-wide. For instance, on x86-64, I can find this information under: /usr/include/asm/unistd_64.h