You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the rangeError types in SchedControl_ConfigureFlags correctly return the expected ranges, it would be nice if the userError message strings also reported those ranges to make them more discoverable.
if (budget_us>MAX_PERIOD_US||budget_ticks<MIN_BUDGET) {
userError("SchedControl_ConfigureFlags: budget out of range.");
current_syscall_error.type=seL4_RangeError;
current_syscall_error.rangeErrorMin=MIN_BUDGET_US;
current_syscall_error.rangeErrorMax=MAX_PERIOD_US;
returnEXCEPTION_SYSCALL_ERROR;
}
the message could say something like
userError("SchedControl_ConfigureFlags: budget out of range [MIN_BUDGET (%ld) .. MAX_PERIOD (%ld)].", MIN_BUDGET_US, MAX_PERIOD_US);
(multiple such range checks in SchedControl_ConfigureFlags)
The text was updated successfully, but these errors were encountered:
While the rangeError types in
SchedControl_ConfigureFlags
correctly return the expected ranges, it would be nice if theuserError
message strings also reported those ranges to make them more discoverable.E.g. here in
the message could say something like
(multiple such range checks in
SchedControl_ConfigureFlags
)The text was updated successfully, but these errors were encountered: