perf_event_uncore: consider capabilities for permissions #201
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Description
Fixed issue #200 by reading capabilities using the
capget
system call. Now, users other thanroot
can use PAPI to read uncore counters, provided they have one of the following capabilities:CAP_SYS_ADMIN
orCAP_PERFMON
.Some rationale and future possibilities
I opted to use the
capget
system call directly, not to addlibcap
as another dependency.I'd like to ask if there's any reason why system call numbers are manually defined. Would there
be any issue arising from the use of the
sys/syscall.h
header?Author Checklist
Why this PR exists. Reference all relevant information, including background, issues, test failures, etc
Commits are self contained and only do one thing
Commits have a header of the form:
module: short description
Commits have a body (whenever relevant) containing a detailed description of the addressed problem and its solution
The PR needs to pass all the tests