At a computer system, the computer system including a physical processor and an operating system having a protected mode and a supervisor mode, wherein protected mode limits program access to physical processor resources of programs running in protected mode, supervisor mode having unlimited access to physical processor resources, one or more functions gating access to supervisor mode to permit a program in protected mode to transition to supervisor mode to access physical processor resources, wherein programs executed within the operating system can transition from protected mode to supervisor mode and from supervisor mode to protected mode depending on program instructions, supervisor mode having a default supervisor mode execution object format being threads that consumes physical processor resources on a time shared basis in accordance with a default supervisor mode scheduling policy, wherein an execution object is an instance of a workload abstraction that consumes resources and is time shared on the physical processor, a method for scheduling the consumption of processor resources in protected mode, the method comprising: an act of allocating physical processor resources to a first execution object of a protected mode scheduling domain within the protected mode scheduling domain, physical processor resources allocated in accordance with a protected mode scheduling policy that differs from the default supervisor mode scheduling policy, wherein the protected mode scheduling policy is for multiplexing execution objects of the protected mode scheduling domain on a virtual processor, the virtual processor mapping at least a portion of the physical processor for use by execution objects of the protected mode scheduling domain; an act of utilizing the allocated physical processor resources to partial complete work indicated in the first execution object; an act of determining, in accordance with the protected mode scheduling policy, that allocation of physical processor resources is to transition to a second execution object within the protected mode scheduling domain prior to fully completing the work indicated in the first execution object; an act of switching context from the first execution object to the second execution object within protected mode and without transitioning to supervisor mode, including: an act of persisting the state of first execution object in an execution object store, the execution object store resident within the protected mode scheduling domain; and an act of loading the state of the second execution object from the execution object store; an act of allocating physical processor resources to the second execution object of a protected mode scheduling domain within the protected mode scheduling domain subsequent to switching context to the second execution object; and an act of utilizing the allocated physical processor resources to partial complete work indicated in the second execution object; wherein protected mode comprises user mode and supervisor mode comprises kernel mode, and wherein kernel mode uses threads and wherein the protected mode scheduling domain is a user mode scheduling domain that uses an execution object format other than threads. an act of allocating physical processor resources to a first execution object of a protected mode scheduling domain within the protected mode scheduling domain, physical processor resources allocated in accordance with a protected mode scheduling policy that differs from the default supervisor mode scheduling policy, wherein the protected mode scheduling policy is for multiplexing execution objects of the protected mode scheduling domain on a virtual processor, the virtual processor mapping at least a portion of the physical processor for use by execution objects of the protected mode scheduling domain; an act of utilizing the allocated physical processor resources to partial complete work indicated in the first execution object; an act of determining, in accordance with the protected mode scheduling policy, that allocation of physical processor resources is to transition to a second execution object within the protected mode scheduling domain prior to fully completing the work indicated in the first execution object; an act of switching context from the first execution object to the second execution object within protected mode and without transitioning to supervisor mode, including: an act of persisting the state of first execution object in an execution object store, the execution object store resident within the protected mode scheduling domain; and an act of loading the state of the second execution object from the execution object store; an act of persisting the state of first execution object in an execution object store, the execution object store resident within the protected mode scheduling domain; and an act of loading the state of the second execution object from the execution object store; an act of allocating physical processor resources to the second execution object of a protected mode scheduling domain within the protected mode scheduling domain subsequent to switching context to the second execution object; and an act of utilizing the allocated physical processor resources to partial complete work indicated in the second execution object; wherein protected mode comprises user mode and supervisor mode comprises kernel mode, and wherein kernel mode uses threads and wherein the protected mode scheduling domain is a user mode scheduling domain that uses an execution object format other than threads.