On Wed, Jun 07, 2023 at 10:05:11AM -0400, Steven Sistare wrote:
> On 2/8/2023 2:22 PM, Peter Xu wrote:
> > On Wed, Feb 08, 2023 at 01:34:18PM -0500, Steven Sistare wrote:
> >> On 2/7/2023 3:23 PM, Peter Xu wrote:
> >>> On Tue, Feb 07, 2023 at 11:03:33AM -0800, Steve Sistare wrote:
> migrate_ig
On 2/8/2023 2:22 PM, Peter Xu wrote:
> On Wed, Feb 08, 2023 at 01:34:18PM -0500, Steven Sistare wrote:
>> On 2/7/2023 3:23 PM, Peter Xu wrote:
>>> On Tue, Feb 07, 2023 at 11:03:33AM -0800, Steve Sistare wrote:
migrate_ignore_shared() is an optimization that avoids copying memory
that is v
On Wed, Feb 08, 2023 at 01:34:18PM -0500, Steven Sistare wrote:
> On 2/7/2023 3:23 PM, Peter Xu wrote:
> > On Tue, Feb 07, 2023 at 11:03:33AM -0800, Steve Sistare wrote:
> >> migrate_ignore_shared() is an optimization that avoids copying memory
> >> that is visible and can be mapped on the target.
On 2/7/2023 3:23 PM, Peter Xu wrote:
> On Tue, Feb 07, 2023 at 11:03:33AM -0800, Steve Sistare wrote:
>> migrate_ignore_shared() is an optimization that avoids copying memory
>> that is visible and can be mapped on the target. However, a
>> memory-backend-ram or a memory-backend-memfd block with t
On Tue, Feb 07, 2023 at 11:03:33AM -0800, Steve Sistare wrote:
> migrate_ignore_shared() is an optimization that avoids copying memory
> that is visible and can be mapped on the target. However, a
> memory-backend-ram or a memory-backend-memfd block with the RAM_SHARED
> flag set is not migrated w
migrate_ignore_shared() is an optimization that avoids copying memory
that is visible and can be mapped on the target. However, a
memory-backend-ram or a memory-backend-memfd block with the RAM_SHARED
flag set is not migrated when migrate_ignore_shared() is true. This is
wrong, because the block