search for: ___gfp_dma

...gt; * require any memory allocations directly (not even GFP_NOWAIT/GFP_ATOMIC) > * or via any lock dependency. Yea, GFP_ATOMIC would do just as well. But I think any allocation on this path would be problematic. How about a flag to make all allocations fail? E.g. #define GFP_FORBIDDEN (___GFP_DMA | ___GFP_HIGHMEM) Still this is not a blocker, we can worry about this later. > > > >> + /* > >> + * This is expected to never fail, because there is always an > >> + * entry available on the vq. > >> + */ > >> + BUG_ON(err); > >&...

...or via any lock dependency. > > > > Yea, GFP_ATOMIC would do just as well. But I think any allocation > > on this path would be problematic. > > > > How about a flag to make all allocations fail? > > > > E.g. > > > > #define GFP_FORBIDDEN (___GFP_DMA | ___GFP_HIGHMEM) > > > > Still this is not a blocker, we can worry about this later. > > > > > > > > > > > >> + /* > > > >> + * This is expected to never fail, because there is always an > > > >> + * entry av...

This patch series is separated from the previous "Virtio-balloon Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_VQ, implemented by this series enables the virtio-balloon driver to report hints of guest free pages to the host. It can be used to accelerate live migration of VMs. Here is an introduction of this usage: Live migration needs to transfer the VM's memory

This patch series is separated from the previous "Virtio-balloon Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_VQ, implemented by this series enables the virtio-balloon driver to report hints of guest free pages to the host. It can be used to accelerate live migration of VMs. Here is an introduction of this usage: Live migration needs to transfer the VM's memory