Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syscount: Use ausyscalls if available to get syscall list #1044

Merged
merged 1 commit into from
Mar 11, 2017

Conversation

goldshtn
Copy link
Collaborator

If ausyscall is installed, it can provide a clean, up-to-date list of
syscall numbers for the current architecture. This is much more useful
than the default hardcoded list for x86-64, which is currently used by
syscount.

Try to run ausyscall --dump and parse the output before resorting to
the static list. Tested on FC/Linux 4.9 and produces 327 syscalls.

Resolves #1001.

If ausyscall is installed, it can provide a clean, up-to-date list of
syscall numbers for the current architecture. This is much more useful
than the default hardcoded list for x86-64, which is currently used by
syscount.

Try to run `ausyscall --dump` and parse the output before resorting to
the static list. Tested on FC/Linux 4.9 and produces 327 syscalls.

Resolves iovisor#1001.
@4ast
Copy link
Member

4ast commented Mar 11, 2017

hmm. how is it better than hardcoded?
syscall numbers will never change.

@goldshtn
Copy link
Collaborator Author

Yes, but:

  1. if a syscall is added we don't have to update bcc
  2. this works on more than just x86-64

@4ast 4ast merged commit eea18dc into iovisor:master Mar 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants