On Wed, 10 Jun 2020 13:54:00 +0200 David Hildenbrand <da...@redhat.com> wrote:
> VFIO is (except devices without a physical IOMMU or some mediated devices) > incompatible with discarding of RAM. The kernel will pin basically all VM > memory. Let's convert to ram_block_discard_disable(), which can now > fail, in contrast to qemu_balloon_inhibit(). > > Leave "x-balloon-allowed" named as it is for now. > > Cc: Cornelia Huck <coh...@redhat.com> > Cc: Alex Williamson <alex.william...@redhat.com> > Cc: Christian Borntraeger <borntrae...@de.ibm.com> > Cc: Tony Krowiak <akrow...@linux.ibm.com> > Cc: Halil Pasic <pa...@linux.ibm.com> > Cc: Pierre Morel <pmo...@linux.ibm.com> > Cc: Eric Farman <far...@linux.ibm.com> > Signed-off-by: David Hildenbrand <da...@redhat.com> > --- > hw/vfio/ap.c | 10 +++---- > hw/vfio/ccw.c | 11 ++++---- > hw/vfio/common.c | 53 +++++++++++++++++++---------------- > hw/vfio/pci.c | 6 ++-- > include/hw/vfio/vfio-common.h | 4 +-- > 5 files changed, 45 insertions(+), 39 deletions(-) Did not have time to review in detail, but looks sane. Acked-by: Cornelia Huck <coh...@redhat.com>
