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.

Sign up for GitHub

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

Jump to bottom

tool: SCHED_DEADLINE should not be set inside QM #376

Closed
dougsland opened this issue Apr 24, 2024 · 0 comments · Fixed by #378
Closed

tool: SCHED_DEADLINE should not be set inside QM #376

dougsland opened this issue Apr 24, 2024 · 0 comments · Fixed by #378
Assignees
@dougsland
Labels
enhancement New feature or request jira

Comments

@dougsland
Copy link
Collaborator

dougsland commented Apr 24, 2024 •
edited

Create a tool to test if it's possible to set SCHED_DEADLINE inside QM partition. It should not be possible.

See-Also: #375
@dougsland dougsland self-assigned this Apr 24, 2024
@dougsland dougsland changed the title tool: SCHED_DEADLINE should not be set inside QM.is set in QM tool: SCHED_DEADLINE should not be set inside QM Apr 24, 2024
@dougsland dougsland added enhancement New feature or request jira labels Apr 24, 2024
This was referenced Apr 24, 2024
Open
Closed
Merged
dougsland added a commit that referenced this issue Apr 24, 2024
@dougsland
tools: add deny_sched_setattr
b7f7cb8 
A tool to test if inside QM it's possible to use the
deny_sched_setattr() syscall to set SCHED_DEADLINE.

Fixes: #376

Signed-off-by: Douglas Schilling Landgraf <dougsland@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dougsland dougsland

Labels
enhancement New feature or request jira
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

tools: add deny_sched_setattr dougsland/qm
1 participant
@dougsland