BackendDriver: Difference between revisions

From Xen
Jump to navigationJump to search
(Created page with "<!-- MoinMoin name: BackendDriver --> <!-- Comment: --> <!-- WikiMedia name: BackendDriver --> <!-- Page revision: 00000003 --> <!-- Original date: Sat Jul 29 16:23:10…")
 
m (Removed multiple apostrophes that were causing a formatting error.)
 
Line 6: Line 6:


__NOTOC__
__NOTOC__
To allow unprivileged [[DomU]]s to share hardware, [[Dom0]] must give them an interface by which to make requests for access to the hardware. This is accomplished by using a [[BackendDriver]]. The [[BackendDriver]] runs in Dom0 or a [[DriverDomain]] and communicates with [[FrontendDriver]]''''''s via [[XenBus]], [[XenStore]], and shared memory pages. It queues requests from [[DomU]]s and relays them to the real hardware driver.
To allow unprivileged [[DomU]]s to share hardware, [[Dom0]] must give them an interface by which to make requests for access to the hardware. This is accomplished by using a [[BackendDriver]]. The [[BackendDriver]] runs in Dom0 or a [[DriverDomain]] and communicates with [[FrontendDriver]]s via [[XenBus]], [[XenStore]], and shared memory pages. It queues requests from [[DomU]]s and relays them to the real hardware driver.


== See also ==
== See also ==

Latest revision as of 13:56, 30 July 2012


To allow unprivileged DomUs to share hardware, Dom0 must give them an interface by which to make requests for access to the hardware. This is accomplished by using a BackendDriver. The BackendDriver runs in Dom0 or a DriverDomain and communicates with FrontendDrivers via XenBus, XenStore, and shared memory pages. It queues requests from DomUs and relays them to the real hardware driver.

See also