Re: [kvm-devel] [patch 0/3] QEMU balloon support

2008-03-17 Thread Avi Kivity
Marcelo Tosatti wrote: Hi Avi, Good that you're back. On Sun, Mar 16, 2008 at 04:00:06PM +0200, Avi Kivity wrote: Marcelo Tosatti wrote: This patchset resends Anthony's QEMU balloon support plus: - Truncates the target size to ram size - Enables madvise() conditioned on

Re: [kvm-devel] [patch 0/3] QEMU balloon support

2008-03-17 Thread Marcelo Tosatti
On Mon, Mar 17, 2008 at 01:11:11PM +0200, Avi Kivity wrote: + up_read(kvm-slots_lock); So as to avoid rmap_nuke, since that will be done through the madvise() path. Why not do it in userspace? I don't see any way of knowing whether you have or not mmu notifiers from

Re: [kvm-devel] [patch 0/3] QEMU balloon support

2008-03-16 Thread Avi Kivity
Marcelo Tosatti wrote: This patchset resends Anthony's QEMU balloon support plus: - Truncates the target size to ram size - Enables madvise() conditioned on KVM_ZAP_GFN ioctl Once mmu notifiers are in, KVM_ZAP_GFN isn't needed. So we have three possible situations: - zap needed, but

Re: [kvm-devel] [patch 0/3] QEMU balloon support

2008-03-16 Thread Marcelo Tosatti
Hi Avi, Good that you're back. On Sun, Mar 16, 2008 at 04:00:06PM +0200, Avi Kivity wrote: Marcelo Tosatti wrote: This patchset resends Anthony's QEMU balloon support plus: - Truncates the target size to ram size - Enables madvise() conditioned on KVM_ZAP_GFN ioctl Once mmu

[kvm-devel] [patch 0/3] QEMU balloon support

2008-03-12 Thread Marcelo Tosatti
This patchset resends Anthony's QEMU balloon support plus: - Truncates the target size to ram size - Enables madvise() conditioned on KVM_ZAP_GFN ioctl -- - This SF.net email is sponsored by: Microsoft Defy all