Problem
The NIST definition of resource starvation did not account for scheduler starvation of a process based on considerations other than insufficient resources. I can think of a situation where I, as root, would want to instruct the scheduler to starve a specific process, deliberately, even if it had important priority and low vruntime. What might be such a situation and why would I do such a thing? (and if so, why not just re-nice it or kill it)?