summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarc-André Lureau <marcandre.lureau@redhat.com>2015-10-07 16:31:47 +0200
committerMarc-André Lureau <marcandre.lureau@redhat.com>2015-10-26 10:19:53 +0100
commit7d4f4bdaf785dfe9fc41b06f85cc9aaf1b1474ee (patch)
tree86f7fa3b33e8816811606da045d0dc042eb9306c
parentf7a199b2b4486242271f769bb4bc2638c0413274 (diff)
doc: document ivshmem & hugepages
Document and give some examples of hugepages support with ivshmem device and server. Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com>
-rw-r--r--qemu-doc.texi13
1 files changed, 13 insertions, 0 deletions
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 <shm size> 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