Linked by diegocg on Mon 1st Oct 2012 16:52 UTC
Thread beginning with comment 537359
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2005-07-08
These days we have things like Thunderbolt which exposes DMA space to external bus devices, so IO virtualization is not just for improving hypervisor performance anymore. We can't continue treating DMA as a shared privileged resource. Each device needs its own isolated and untrusted address space, much like userspace. If the devices have their own DMA space, then their drivers no longer need to run in kernel mode, and supporting userspace drivers just becomes a matter of providing a syscall interface for allocating DMA space.