[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [libvirt] [PATCH 3/4] qemu: set qemu process' RLIMIT_MEMLOCK when VFIO is used



On Thu, Apr 25, 2013 at 09:44:32PM -0400, Laine Stump wrote:
> VFIO requires all of the guest's memory and IO space to be lockable in
> RAM. The domain's max_balloon is the maximum amount of memory the
> domain can have (in KiB). We add a generous 1GiB to that for IO space
> (still much better than KVM device assignment, where the KVM module
> actually *ignores* the process limits and locks everything anyway),
> and convert from KiB to bytes.
> 
> In the case of hotplug, we are changing the limit for the already
> existing qemu process (prlimit() is used under the hood), and for
> regular commandline additions of vfio devices, we schedule a call to
> setrlimit() that will happen after the qemu process is forked.
> ---
>  src/qemu/qemu_command.c | 25 ++++++++++++++++++-------
>  src/qemu/qemu_hotplug.c | 27 ++++++++++++++++++++-------
>  2 files changed, 38 insertions(+), 14 deletions(-)

ACK


Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]