PRs for tag 'sched_ule'
This is an experimental report containing PRs for tag 'sched_ule' as of 5-30-2014. GNATS has no finer-grained categorization than 'kern', 'bin', 'ports', and so forth. To augment this, the bugmeisters have adopted the convention of adding '[<tagname>]' to the Synopsis field. Consider this a prototype of a better search function.
This report is generated statically.
Please give feedback on this report to linimon@FreeBSD.org. Thanks.
PRs for tag 'sched_ule':
| S | Submitted | Tracker | Resp. | Description |
|---|---|---|---|---|
| o | 2012/04/02 | kern/166568 | [sched_ule] intr stuck in WAIT state | |
| o | 2011/12/24 | kern/163587 | [sched_ule] The ULE scheduler does not load in the fourth core processor i3 | |
| o | 2011/09/28 | kern/161097 | [sched_ule] Unkillable process hanging waiting for "exithold" when p_lock is 1 | |
| o | 2008/10/17 | kern/128177 | jeff | [sched_ule] wrong CPU usage reported by top(1)/ps(1) with SCHED_ULE |
| o | 2007/10/23 | kern/117420 | jeff | [sched_ule] round off in sched_balance_pair() |
| s | 2005/09/02 | kern/85658 | jeff | [sched_ule] [patch] add DDB command, show runq, to sched_ule.c |
Bugs can be in one of several states:
- o - open
- A problem report has been submitted, no sanity checking performed.
- a - analyzed
- The problem is understood and a solution is being sought.
- f - feedback
- Further work requires additional information from the originator or the community - possibly confirmation of the effectiveness of a proposed solution.
- p - patched
- A patch has been committed, but some issues (MFC and / or confirmation from originator) are still open.
- r - repocopy
- The resolution of the problem report is dependent on a repocopy operation within the CVS repository which is awaiting completion.
- s - suspended
- The problem is not being worked on, due to lack of information or resources. This is a prime candidate for somebody who is looking for a project to do. If the problem cannot be solved at all, it will be closed, rather than suspended.
- c - closed
- A problem report is closed when any changes have been integrated, documented, and tested -- or when fixing the problem is abandoned.