tools/libxencall: use hypercall buffer device if available
authorJuergen Gross <jgross@suse.com>
Mon, 18 Jun 2018 07:18:54 +0000 (09:18 +0200)
committerIan Jackson <Ian.Jackson@eu.citrix.com>
Mon, 18 Jun 2018 11:31:45 +0000 (12:31 +0100)
commit33be2c385823e67c773527366a5d5e8ffe78d046
tree745a1c9bc8018cca1f835b68f6ec6d8bc2d74710
parente23d2234e08872ac1c719f3e338994581483440f
tools/libxencall: use hypercall buffer device if available

Instead of using anonymous memory for hypercall buffers which is then
locked into memory, use the hypercall buffer device of the Linux
privcmd driver if available.

This has the advantage of needing just a single mmap() for allocating
the buffer and page migration or compaction can't make the buffer
unaccessible for the hypervisor.

Signed-off-by: Juergen Gross <jgross@suse.com>
Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
tools/libs/call/core.c
tools/libs/call/linux.c
tools/libs/call/private.h