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

Running with idle priority on Linux leads to "mono_thread_internal_set_priority: unknown policy 5" warnings #20683

Open
WGH- opened this issue Dec 20, 2020 · 0 comments · May be fixed by #21705

Comments

@WGH-
Copy link

WGH- commented Dec 20, 2020

Steps to Reproduce

  1. chrt --idle 0 csc

Current Behavior

mono_thread_internal_set_priority: unknown policy 5
Microsoft (R) Visual C# Compiler version 3.6.0-4.20224.5 (ec77c100)
Copyright (C) Microsoft Corporation. All rights reserved.

warning CS2008: No source files specified.
error CS1562: Outputs without source must have the /out option specified

Expected Behavior

No such warnings occur.

On which platforms did you notice this

[ ] macOS
[x] Linux
[ ] Windows

Version Used:

6.10.0.104 (the code appears to be the same on master)

Notes

In mono/metadata/threads.c, the case SCHED_IDLE appears to be unhandled.

nekopsykose added a commit to nekopsykose/mono that referenced this issue Sep 8, 2023
use the 0 path (man 7 sched):
 For threads scheduled under one of the normal scheduling policies
 (SCHED_OTHER, SCHED_IDLE, SCHED_BATCH), sched_priority is not used in
 scheduling decisions (it must be specified as 0).

This change is released under the MIT license.
closes mono#20683
nekopsykose added a commit to nekopsykose/mono that referenced this issue Sep 8, 2023
use the 0 path (man 7 sched):
 For threads scheduled under one of the normal scheduling policies
 (SCHED_OTHER, SCHED_IDLE, SCHED_BATCH), sched_priority is not used in
 scheduling decisions (it must be specified as 0).

This change is released under the MIT license.
closes mono#20683
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 a pull request may close this issue.

1 participant