* Matthew Khouzam ([email protected]) wrote: > Hi, I was tracing some simple programs and came up with a list of > "sys_unknown" tracepoints. This may or may not help for developers to > see what they are. > > sys_unknown id = 11 => exec_ve > sys_unknown id = 119 => sigreturn > sys_unknown id = 120 => clone > sys_unknown id = 184 => capget > sys_unknown id = 185 => capset > sys_unknown id = 194 => ftruncate (?) confirm please > sys_unknown id = 243 => set_thread_area (?) confirm please > sys_unknown id = 250 => fadvise (?) confirm please > sys_unknown id = 314 => sync_file_range (?) confirm please
See the _override files, that allow you to declare them by yourself. Those are probably missing in the DEFINE_SYSCALL(*) in the kernel, so we need to create them in the override files (they cannot be automatically generated). Patches are welcome, Thanks, Mathieu > > _______________________________________________ > ltt-dev mailing list > [email protected] > http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev > -- Mathieu Desnoyers Operating System Efficiency R&D Consultant EfficiOS Inc. http://www.efficios.com _______________________________________________ ltt-dev mailing list [email protected] http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
