On 08/10/2019 13:34, Lars Kurth wrote: > > On 03/10/2019, 21:59, "Andrew Cooper" <andrew.coop...@citrix.com> wrote: > > Put together an introduction page for the Sphinx/RST docs, along with a > glossary which will accumulate over time. > > Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com> > > Reviewed-by: Lars Kurth <lars.ku...@citrix.com>
Thanks. > > There were a few minor improvements which could be made, I am listing these > below, but none are show-stoppers. > > +Xen is an open source, bare metal hypervisor. It runs as the most > privileged > +piece of software, and shares the resources of the hardware between > virtual > Maybe better: s/software/software on the system/ or s/software/software on > the host/ Fixed. > +machines. > > + hardware domain > + A :term:`domain`, commonly dom0, which shares responsibility with > Xen > + about the system as a whole. > + > + By default it gets all devices, including all disks and network > cards, so > + is responsible for multiplexing guest I/O > > This is a little unclear: in particular the 1st paragraph. Earlier you talk > about hardware > domain="responsible for hardware and marshalling guest I/O", which is > clearer. > > Maybe: > > A :term:`domain`, commonly dom0, which hosts all devices, including disks > and network cards and is responsible for multiplexing guest I/O > > is better Sadly, its not accurate. Multiplexing of I/O is only in the case that device driver domains aren't in use. The other example you cite is a description of the associated image. There are things besides I/O which the hardware domain is responsible for, such as APCI OPSM (but only in x86), and system reboot etc. I have left the description as-is, for lack of an obviously better way of expressing things. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
