sysenter/sysexit depends more on your CPU than the kernel - Linux has utilized it since the early 2.5 days. Linux picks either SYSENTER, SYSCALL or legacy int 80 methods depending on what type of CPU it is running on.
Not sure how you could confirm that it's actually being used. I don't think Systemtap or LTT will look at a low enough level. Maybe you could instrument the kernel and add some tracepoints in the vDSO code...
You might consider looking into SystemTap. With that, you should be able to write a script that triggers an action whenever an event of your liking, including system calls, occurs.
sysenter/sysexit depends more on your CPU than the kernel - Linux has utilized it since the early 2.5 days. Linux picks either SYSENTER, SYSCALL or legacy int 80 methods depending on what type of CPU it is running on.
Not sure how you could confirm that it's actually being used. I don't think Systemtap or LTT will look at a low enough level. Maybe you could instrument the kernel and add some tracepoints in the vDSO code...
Only suggestion I can think of would be to use the Linux Trace Toolkit to create a kernel dump and dig through the system calls.
You might consider looking into SystemTap. With that, you should be able to write a script that triggers an action whenever an event of your liking, including system calls, occurs.