forked from xen-project/xen
-
Notifications
You must be signed in to change notification settings - Fork 17
Shared coprocessor framework
Andrii Anisov edited this page Oct 19, 2016
·
17 revisions
The main idea of the coprocessor sharing is to let different domains use coprocessor concurrently and independently within some time share.
It is targeted capability of different domains to run concurrently different firmware on the coproc. This target implies that there is a way to switch coproc execution context externally from the main CPU which is running a hypervisor.
From our previous experience it is clear that complexity and predictability of a coprocessor externally issued context switching process defines the accuracy of the coproc scheduling and resources allocation for domains as well as scheduling overhead.
How should we perform coprocessor PRCM (who does, how to handle domains PRCM operations, etc)?