[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs
From: |
Peter Xu |
Subject: |
Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs |
Date: |
Fri, 15 Mar 2024 12:05:22 -0400 |
[I queued patch 1-2 into -stable, leaving this patch for further
discussions]
On Fri, Mar 15, 2024 at 08:55:42AM +0000, Daniel P. Berrangé wrote:
> The 'file:' protocol eventually calls into qemu_open, and this
> transparently allows for FD passing using /dev/fdset/NNN syntax
> to pass in FDs.
If it always use /dev/fdsets for files, does it mean that the newly added
SOCKET_ADDRESS_TYPE_FD support on mapped-ram will never be used (so we can
drop them)?
What about the old getfd? Is it obsolete because it relies on monitor
object? Or maybe it's still in use?
It would be greatly helpful if there can be a summary of how libvirt uses
fd for migration purpose.
Thanks,
--
Peter Xu
- [PATCH v3 0/3] migration mapped-ram fixes, Fabiano Rosas, 2024/03/14
- [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Fabiano Rosas, 2024/03/14
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Daniel P . Berrangé, 2024/03/15
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs,
Peter Xu <=
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Fabiano Rosas, 2024/03/15
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Peter Xu, 2024/03/15
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Daniel P . Berrangé, 2024/03/19
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Peter Xu, 2024/03/19
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Daniel P . Berrangé, 2024/03/19
- Re: [RFC PATCH v3 3/3] migration: Add fd to FileMigrationArgs, Peter Xu, 2024/03/19
[PATCH v3 1/3] migration/multifd: Ensure we're not given a socket for file migration, Fabiano Rosas, 2024/03/14
[PATCH v3 2/3] migration/multifd: Duplicate the fd for the outgoing_args, Fabiano Rosas, 2024/03/14