Received: from eggs.gnu.org ([2001:4830:134:3::10]:33780) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1H37-0002p4-KL for qemu-devel@nongnu.org; Tue, 24 Nov 2015 12:06:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a1H33-0005l4-Eu for qemu-devel@nongnu.org; Tue, 24 Nov 2015 12:06:37 -0500 Received: from mx1.redhat.com ([209.132.183.28]:35472) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a1H33-0005kS-8g for qemu-devel@nongnu.org; Tue, 24 Nov 2015 12:06:33 -0500 From: Markus Armbruster Date: Tue, 24 Nov 2015 18:06:25 +0100 Message-Id: <1448384789-14830-2-git-send-email-armbru@redhat.com> In-Reply-To: <1448384789-14830-1-git-send-email-armbru@redhat.com> References: <1448384789-14830-1-git-send-email-armbru@redhat.com> Subject: [Qemu-devel] [PATCH for-2.5 1/5] qemu-doc: Fix ivshmem example markup List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: marcandre.lureau@redhat.com, claudio.fontana@huawei.com Use @var{foo} like we do everywhere else, not . Signed-off-by: Markus Armbruster --- qemu-doc.texi | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/qemu-doc.texi b/qemu-doc.texi index 460ab71..c9b7069 100644 --- a/qemu-doc.texi +++ b/qemu-doc.texi @@ -1256,7 +1256,7 @@ zero-copy communication to the application level of the guests. The basic syntax is: @example -qemu-system-i386 -device ivshmem,size=[,shm=] +qemu-system-i386 -device ivshmem,size=@var{size}[,shm=@var{shm-name}] @end example If desired, interrupts can be sent between guest VMs accessing the same shared @@ -1267,12 +1267,12 @@ memory server is: @example # First start the ivshmem server once and for all -ivshmem-server -p -S -m -l -n +ivshmem-server -p @var{pidfile} -S @var{path} -m @var{shm-name} -l @var{shm-size} -n @var{vectors} # Then start your qemu instances with matching arguments -qemu-system-i386 -device ivshmem,size=,vectors=,chardev= +qemu-system-i386 -device ivshmem,size=@var{shm-size},vectors=@var{vectors},chardev=@var{id} [,msi=on][,ioeventfd=on][,role=peer|master] - -chardev socket,path=,id= + -chardev socket,path=@var{path},id=@var{id} @end example When using the server, the guest will be assigned a VM ID (>=0) that allows guests -- 2.4.3