aboutsummaryrefslogtreecommitdiff
path: root/rust/qemu-api-macros
diff options
context:
space:
mode:
authorZhao Liu <zhao1.liu@intel.com>2025-04-14 22:49:42 +0800
committerPaolo Bonzini <pbonzini@redhat.com>2025-05-02 17:37:46 +0200
commitdb46654af893abed53dce35ebab86056ac9b3004 (patch)
tree748cbaa355208b416b820544c69e756f4b64708b /rust/qemu-api-macros
parent8d9502b4e947a9cfcf1d1940cc70d1579b53ecaf (diff)
downloadqemu-db46654af893abed53dce35ebab86056ac9b3004.zip
qemu-db46654af893abed53dce35ebab86056ac9b3004.tar.gz
qemu-db46654af893abed53dce35ebab86056ac9b3004.tar.bz2
rust/hpet: Support migration
Based on commit 1433e38cc8 ("hpet: do not overwrite properties on post_load"), add the basic migration support to Rust HPET. The current migration implementation introduces multiple unsafe callbacks. Before the vmstate builder, one possible cleanup approach is to wrap callbacks in the vmstate binding using a method similar to the vmstate_exist_fn macro. However, this approach would also create a lot of repetitive code (since vmstate has so many callbacks: pre_load, post_load, pre_save, post_save, needed and dev_unplug_pending). Although it would be cleaner, it would somewhat deviate from the path of the vmstate builder. Therefore, firstly focus on completing the functionality of HPET, and those current unsafe callbacks can at least clearly indicate the needed functionality of vmstate. The next step is to consider refactoring vmstate to move towards the vmstate builder direction. Additionally, update rust.rst about Rust HPET can support migration. Signed-off-by: Zhao Liu <zhao1.liu@intel.com> Link: https://lore.kernel.org/r/20250414144943.1112885-9-zhao1.liu@intel.com Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'rust/qemu-api-macros')
0 files changed, 0 insertions, 0 deletions