Re: [PATCH v2 0/3] vhost: memslot handling improvements

["Michael S. Tsirkin" <mst@redhat.com>]

On Wed, May 03, 2023 at 04:16:10PM +0200, David Hildenbrand wrote:
> On 20.04.23 16:28, Igor Mammedov wrote:
> > On Thu, 16 Mar 2023 16:36:55 +0100
> > David Hildenbrand <david@redhat.com> wrote:
> > 
> > > Following up on my previous work to make virtio-mem consume multiple
> > > memslots dynamically [1] that requires precise accounting between used vs.
> > > reserved memslots, I realized that vhost makes this extra hard by
> > > filtering out some memory region sections (so they don't consume a
> > > memslot) in the vhost-user case, which messes up the whole memslot
> > > accounting.
> > > 
> > > This series fixes what I found to be broken and prepares for more work on
> > > [1]. Further, it cleanes up the merge checks that I consider unnecessary.
> > 
> > Acked-by: Igor Mammedov <imammedo@redhat.com>
> 
> Thanks Igor!
> 
> @MST, do you want to these patches (I can resend in case it's easier to
> fixup the typo in patch #3).
> 
> Alternatively, I could send these patches along with another memory-backend
> patch I have queued.

I think I'll queue them to make sure
there are no conflicts. Pls do post with a typo fixed. Thanks!





> -- 
> Thanks,
> 
> David / dhildenb