[LITMUS^RT] Supporting Job Aborts

[Björn Brandenburg]

On 07.09.2012, at 19:29, Jonathan Herman <hermanjl at cs.unc.edu> wrote:

> For Glenn's current issue, setitimer may give the correct result. I
> can imagine other situations where it wouldn't work. Suppose some kind
> of slack stealing is in effect, and the current task overexecutes, but
> this can be handled by the slack. We don't want the timer going off
> and having the task quit in this case.

In that case, I'd add a flag to mark the timer (or task) as "postponable on slack donation". Then the expiry time of the timer could be pushed back automatically on slack donation (and even advanced when, say, stealing budget from low-criticality tasks). 

In any case, instead of introducing new signals and mechanisms, I'd first try to layer an implementation on top of the existing itimer infrastructure and reuse the corresponding signals.

Just my two cents...

- Björn