syscall: syscall_wraps apply to kernel side symbols as well about nuttx

[xiaoxiang781216]

--wrap is only used in the flat build, for kernel/protected build the hook come from syscall.csv.

[pussuw]

When SCHED_INSTRUMENTATION_SYSCALL is enabled, --wrap is used to generate wrappers that encapsulate the system call itself into:

int __wrap_syscall_xx(int nr, ...)
{
  sched_note_syscall_enter(int nr, int argc, ...);
  result = __real_syscall_xx();
  sched_note_syscall_leave(int nr, uintptr_t result);
  return result;
}

This is done for every symbol in the syscall table, which includes nxsem_xx et al. The OS calls them directly and as they are now wrapped, they execute the same __wrap_sem_xx call. This is problematic, as it impacts performance as well as clutters the instrumentation with calls that are not system calls from user space (which is what I want to instrument).

[xiaoxiang781216]

Ok, I forget that only the initial version doesn't use --wrap. @YuuichiNakamura switch to --wrap to support the syscall instrumentation in flat build. One possible fix is moving --wrap from kernel bin to userspace libc.