On Mon, Mar 11, 2024 at 12:03:41PM +, Daniel P. Berrangé wrote:
> On Mon, Mar 04, 2024 at 09:26:32AM +0800, pet...@redhat.com wrote:
> > From: Fabiano Rosas
> >
> > If we receive a file descriptor that points to a regular file, there's
> > nothing stopping us from doing multifd migration with
On Mon, Mar 04, 2024 at 09:26:32AM +0800, pet...@redhat.com wrote:
> From: Fabiano Rosas
>
> If we receive a file descriptor that points to a regular file, there's
> nothing stopping us from doing multifd migration with mapped-ram to
> that file.
>
> Enable the fd: URI to work with multifd + map
On Mon, 11 Mar 2024 at 11:50, Peter Maydell wrote:
>
> On Mon, 4 Mar 2024 at 01:28, wrote:
> >
> > From: Fabiano Rosas
> >
> > If we receive a file descriptor that points to a regular file, there's
> > nothing stopping us from doing multifd migration with mapped-ram to
> > that file.
> >
> > Ena
On Mon, 4 Mar 2024 at 01:28, wrote:
>
> From: Fabiano Rosas
>
> If we receive a file descriptor that points to a regular file, there's
> nothing stopping us from doing multifd migration with mapped-ram to
> that file.
>
> Enable the fd: URI to work with multifd + mapped-ram.
>
> Note that the fds
From: Fabiano Rosas
If we receive a file descriptor that points to a regular file, there's
nothing stopping us from doing multifd migration with mapped-ram to
that file.
Enable the fd: URI to work with multifd + mapped-ram.
Note that the fds passed into multifd are duplicated because we want
to
