[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Driver domain on ARM questions


Looking into thisÂhttp://www.gossamer-threads.com/lists/xen/devel/342003 slides I see that dom0 could be pretty thin, with no device drivers at all. But it is just a picture:)
I suppose that, at least block device should be in dom0 in order to not load huge ramdisk with tools, VM images, etc.

What we actually estimate on our site is a thin dom0 with minimum number of device drivers and minimal functionality. This domain should only start and check other domains are alive. Driver domain should handle most of hardware and provide correspondent backends.

BTW, the actual series should not be used in production but only for
internal testing ;).
Our current intention is not a production, rather POC ;)

A device may have other dependencies (such as the clock, phy...).Â
Yep, separating the HW between different domains is really painful.
Andrii Anisov | Team Lead
Kyiv, 03038, Protasov Business Park, M.Grinchenka, 2/1
P +38.044.492.9695x3664Â M +380505738852 ÂS andriyanisov


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.