Re: [PATCH v3 10/14] migration/ram: Introduce 'fixed-ram' migration stream capability

2023-03-20 Thread Claudio Fontana
Added Fabiano to the thread, CLaudio On 3/20/23 12:05, Claudio Fontana wrote: > On 2/10/23 18:11, Daniel P. Berrangé wrote: >> On Fri, Oct 28, 2022 at 01:39:10PM +0300, Nikolay Borisov wrote: >>> Implement 'fixed-ram' feature. The core of the feature is to ensure that >>> each ram page of the mig

Re: [PATCH v3 10/14] migration/ram: Introduce 'fixed-ram' migration stream capability

2023-03-20 Thread Claudio Fontana
On 2/10/23 18:11, Daniel P. Berrangé wrote: > On Fri, Oct 28, 2022 at 01:39:10PM +0300, Nikolay Borisov wrote: >> Implement 'fixed-ram' feature. The core of the feature is to ensure that >> each ram page of the migration stream has a specific offset in the >> resulting migration stream. The reason

Re: [PATCH v3 10/14] migration/ram: Introduce 'fixed-ram' migration stream capability

2023-02-10 Thread Daniel P . Berrangé
On Fri, Oct 28, 2022 at 01:39:10PM +0300, Nikolay Borisov wrote: > Implement 'fixed-ram' feature. The core of the feature is to ensure that > each ram page of the migration stream has a specific offset in the > resulting migration stream. The reason why we'd want such behavior are > two fold: > >

[PATCH v3 10/14] migration/ram: Introduce 'fixed-ram' migration stream capability

2022-10-28 Thread Nikolay Borisov
Implement 'fixed-ram' feature. The core of the feature is to ensure that each ram page of the migration stream has a specific offset in the resulting migration stream. The reason why we'd want such behavior are two fold: - When doing a 'fixed-ram' migration the resulting file will have a bound