From 7d4f4bdaf785dfe9fc41b06f85cc9aaf1b1474ee Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marc-Andr=C3=A9=20Lureau?= Date: Wed, 7 Oct 2015 16:31:47 +0200 Subject: doc: document ivshmem & hugepages MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Document and give some examples of hugepages support with ivshmem device and server. Signed-off-by: Marc-André Lureau Reviewed-by: Eric Blake --- qemu-doc.texi | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'qemu-doc.texi') diff --git a/qemu-doc.texi b/qemu-doc.texi index afa226303b..3126abdcd3 100644 --- a/qemu-doc.texi +++ b/qemu-doc.texi @@ -1293,6 +1293,19 @@ copy the shared memory on migration to the destination host. With With the @option{peer} case, the device should be detached and then reattached after migration using the PCI hotplug support. +@subsubsection ivshmem and hugepages + +Instead of specifying the using POSIX shm, you may specify +a memory backend that has hugepage support: + +@example +qemu-system-i386 -object memory-backend-file,size=1G,mem-path=/mnt/hugepages,id=mb1 + -device ivshmem,memdev=mb1 +@end example + +ivshmem-server also supports hugepages mount points with the +@option{-m} memory path argument. + @node direct_linux_boot @section Direct Linux Boot -- cgit v1.2.1