On Fri, Nov 11, 2016 at 10:43 PM, Konrad Rzeszutek Wilk <konrad.w...@oracle.com> wrote: > Does this also mean that the hypervisor has to know the co-processors? > As in how to start/stop them? And how to tell them to save/restore > guest context? Or is there some generic specification for doing this?
Unfortunately there is be no single way to switch context on co-processors, so yes, hypervisor has to know the co-processors. The situation is not as bad as having full-scope driver (which is implemented in some proprietary hypervisors), we only need to: 1. stop 2. flush registers 3. switch memory context <--- implemented by SMMU in ARM 4. restore registers 5. start Best regards, Artem Mygaiev _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel