On 06/20/2014 06:15 AM, David Marchand wrote: > Add some notes on the parts needed to use ivshmem devices: more specifically, > explain the purpose of an ivshmem server and the basic concept to use the > ivshmem devices in guests. > > Signed-off-by: David Marchand <david.marchand@xxxxxxxxx> > --- > docs/specs/ivshmem_device_spec.txt | 41 ++++++++++++++++++++++++++++++------ > 1 file changed, 35 insertions(+), 6 deletions(-) > > diff --git a/docs/specs/ivshmem_device_spec.txt b/docs/specs/ivshmem_device_spec.txt > index 667a862..7d2b73f 100644 > --- a/docs/specs/ivshmem_device_spec.txt > +++ b/docs/specs/ivshmem_device_spec.txt > @@ -85,12 +85,41 @@ events have occurred. The semantics of interrupt vectors are left to the > user's discretion. > > > +IVSHMEM host services > +--------------------- > + > +This part is optional (see *Usage in the Guest* section below). > + > +To handle notifications between users of a ivshmem device, a ivshmem server has s/a ivshmem/an ivshmem/ (twice) > +been added. This server is responsible for creating the shared memory and > +creating a set of eventfds for each users of the shared memory. It behaves as a > +proxy between the different ivshmem clients (QEMU): giving the shared memory fd > +to each client, allocating eventfds to new clients and broadcasting to all > +clients when a client disappears. > + > +Apart from the current ivshmem implementation in QEMU, a ivshmem client can be and again > +written for debug, for development purposes, or to implement notifications > +between host and guests. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
Attachment:
signature.asc
Description: OpenPGP digital signature
