Re: [PATCH for-9.1 v5 10/14] migration: Introduce ram_bitmaps

qemu-devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH for-9.1 v5 10/14] migration: Introduce ram_bitmaps_destroy()

From:	Fabiano Rosas
Subject:	Re: [PATCH for-9.1 v5 10/14] migration: Introduce ram_bitmaps_destroy()
Date:	Wed, 20 Mar 2024 11:49:14 -0300

Cédric Le Goater <clg@redhat.com> writes:

> We will use it in ram_init_bitmaps() to clear the allocated bitmaps when
> support for error reporting is added to memory_global_dirty_log_start().
>
> Signed-off-by: Cédric Le Goater <clg@redhat.com>

Reviewed-by: Fabiano Rosas <farosas@suse.de>

[Prev in Thread]

Current Thread

[Next in Thread]

[PATCH for-9.1 v5 08/14] migration: Add Error** argument to .load_setup() handler, (continued)
- [PATCH for-9.1 v5 08/14] migration: Add Error** argument to .load_setup() handler, Cédric Le Goater, 2024/03/20
  - Re: [PATCH for-9.1 v5 08/14] migration: Add Error** argument to .load_setup() handler, Markus Armbruster, 2024/03/20
    - Re: [PATCH for-9.1 v5 08/14] migration: Add Error** argument to .load_setup() handler, Cédric Le Goater, 2024/03/20
- [PATCH for-9.1 v5 07/14] migration: Add Error** argument to .save_setup() handler, Cédric Le Goater, 2024/03/20
- [PATCH for-9.1 v5 09/14] memory: Add Error** argument to .log_global_start() handler, Cédric Le Goater, 2024/03/20
  - Re: [PATCH for-9.1 v5 09/14] memory: Add Error** argument to .log_global_start() handler, Peter Xu, 2024/03/20
    - Re: [PATCH for-9.1 v5 09/14] memory: Add Error** argument to .log_global_start() handler, Cédric Le Goater, 2024/03/20
    - Re: [PATCH for-9.1 v5 09/14] memory: Add Error** argument to .log_global_start() handler, Peter Xu, 2024/03/20
- [PATCH for-9.1 v5 10/14] migration: Introduce ram_bitmaps_destroy(), Cédric Le Goater, 2024/03/20
  - Re: [PATCH for-9.1 v5 10/14] migration: Introduce ram_bitmaps_destroy(), Peter Xu, 2024/03/20
  - Re: [PATCH for-9.1 v5 10/14] migration: Introduce ram_bitmaps_destroy(), Fabiano Rosas <=
- [PATCH for-9.1 v5 12/14] migration: Add Error** argument to ram_state_init(), Cédric Le Goater, 2024/03/20
  - Re: [PATCH for-9.1 v5 12/14] migration: Add Error** argument to ram_state_init(), Fabiano Rosas, 2024/03/20
- [PATCH for-9.1 v5 13/14] migration: Add Error** argument to xbzrle_init(), Cédric Le Goater, 2024/03/20
  - Re: [PATCH for-9.1 v5 13/14] migration: Add Error** argument to xbzrle_init(), Fabiano Rosas, 2024/03/20
- [PATCH for-9.1 v5 11/14] memory: Add Error** argument to the global_dirty_log routines, Cédric Le Goater, 2024/03/20
  - Re: [PATCH for-9.1 v5 11/14] memory: Add Error** argument to the global_dirty_log routines, Fabiano Rosas, 2024/03/20
  - Re: [PATCH for-9.1 v5 11/14] memory: Add Error** argument to the global_dirty_log routines, Peter Xu, 2024/03/20
    - Re: [PATCH for-9.1 v5 11/14] memory: Add Error** argument to the global_dirty_log routines, Yong Huang, 2024/03/21
    - Re: [PATCH for-9.1 v5 11/14] memory: Add Error** argument to the global_dirty_log routines, Peter Xu, 2024/03/22
- [PATCH for-9.1 v5 14/14] migration: Modify ram_init_bitmaps() to report dirty tracking errors, Cédric Le Goater, 2024/03/20

Prev by Date: Re: [PATCH] configure: Fix error message when C compiler is not working
Next by Date: Re: [PATCH for-9.1 v5 11/14] memory: Add Error** argument to the global_dirty_log routines
Previous by thread: Re: [PATCH for-9.1 v5 10/14] migration: Introduce ram_bitmaps_destroy()
Next by thread: [PATCH for-9.1 v5 12/14] migration: Add Error** argument to ram_state_init()
Index(es):
- Date
- Thread