On Fri, 2011-12-09 at 16:35 -0700, Eric Blake wrote: > Improve the documentation of what forms a valid <address> element, > since these elements appear in numerous devices. Thanks for doing that, minor rewrite on this one: > + <dt><code>type='spapr-vio'</code></dt> > + <dd>On PowerPC guests, devices are assigned on the SPAPR-VIO > + bus, which is a flat 64-bit address space, where each address > + should be aligned on a multiple of 0x1000. Each address has > + the following additional attribute: <code>reg</code> (the hex > + value address of the starting > + register). I would say something like: On PowerPC pseries guests, devices can be assigned to the SPAPR VIO bus. It has a flat 64-bit address space, by convention devices are generally located at a multiple of 0x1000, but other addresses are legal and accepted by libvirt. A device can be given an address by specifying the <code>reg</code> attribute, this gives the 64-bit address of the device. If no <code>reg</code> value is specified libvirt will attempt to assign a value for you. cheers
Attachment:
signature.asc
Description: This is a digitally signed message part
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list