From: Peter Xu <peterx@redhat.com>
To: Daniel Henrique Barboza <dbarboza@ventanamicro.com>
Cc: TANG Tiancheng <lyndra@linux.alibaba.com>,
qemu-devel@nongnu.org, Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Weiwei Li <liwei1518@gmail.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
qemu-riscv@nongnu.org, Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH 2/3] hw/intc: Save timers array in RISC-V mtimer VMState
Date: Tue, 9 Sep 2025 17:34:25 -0400 [thread overview]
Message-ID: <aMCdYUZyQWQ4Qc4v@x1.local> (raw)
In-Reply-To: <aa5ea2e9-8d01-4d45-99fc-efa5e6061c8b@ventanamicro.com>
On Tue, Sep 09, 2025 at 09:45:07AM -0300, Daniel Henrique Barboza wrote:
>
>
> On 9/9/25 6:46 AM, TANG Tiancheng wrote:
> > The current 'timecmp' field in vmstate_riscv_mtimer is insufficient to keep
> > timers functional after migration.
> >
> > If an mtimer's entry in 'mtimer->timers' is active at the time the snapshot
> > is taken, it means riscv_aclint_mtimer_write_timecmp() has written to
> > 'mtimecmp' and scheduled a timer into QEMU's main loop 'timer_list'.
> >
> > During snapshot save, these active timers must also be migrated; otherwise,
> > after snapshot load there is no mechanism to restore 'mtimer->timers' back
> > into the 'timer_list', and any pending timer events would be lost.
> >
> > QEMU's migration framework commonly uses VMSTATE_TIMER_xxx macros to save
> > and restore 'QEMUTimer' variables. However, 'timers' is a pointer array
> > with variable length, and vmstate.h did not previously provide a helper
> > macro for such type.
> >
> > This commit adds a new macro, 'VMSTATE_TIMER_PTR_VARRAY', to handle saving
> > and restoring a variable-length array of 'QEMUTimer *'. We then use this
> > macro to migrate the 'mtimer->timers' array, ensuring that timer events
> > remain scheduled correctly after snapshot load.
> >
> > Reviewed-by: LIU Zhiwei <zhiwei_liu@linux.alibaba.com>
> > Signed-off-by: TANG Tiancheng <lyndra@linux.alibaba.com>
> > ---
>
> LGTM but I wonder if changing one of the VMSTATE_TIMER_xxxx macros to accept
> variable length arrays is better than creating a new macro that only RISC-V
> cares about. Creating a new macro surely is easier and less messier than
> changing all existing callers though ...
>
> I'll let the migration folks weight in. Thanks,
I didn't see a 2nd user, though..
I'd split VMSTATE_VARRAY_OF_POINTER_UINT32() into a separate patch, then
define VMSTATE_TIMER_PTR_VARRAY() in riscv .c files if that's the only
user, and if that helps readability.
Thanks,
>
> Daniel
>
>
>
> > hw/intc/riscv_aclint.c | 6 ++++--
> > include/migration/vmstate.h | 14 ++++++++++++++
> > 2 files changed, 18 insertions(+), 2 deletions(-)
> >
> > diff --git a/hw/intc/riscv_aclint.c b/hw/intc/riscv_aclint.c
> > index 318a9c8248432a8cd4c3f3fa990739917ecf7ca1..9f4c36e965e2aa379d75c0a9f656177f0dd82a45 100644
> > --- a/hw/intc/riscv_aclint.c
> > +++ b/hw/intc/riscv_aclint.c
> > @@ -323,13 +323,15 @@ static void riscv_aclint_mtimer_reset_enter(Object *obj, ResetType type)
> > static const VMStateDescription vmstate_riscv_mtimer = {
> > .name = "riscv_mtimer",
> > - .version_id = 2,
> > - .minimum_version_id = 2,
> > + .version_id = 3,
> > + .minimum_version_id = 3,
> > .fields = (const VMStateField[]) {
> > VMSTATE_UINT64(time_delta, RISCVAclintMTimerState),
> > VMSTATE_VARRAY_UINT32(timecmp, RISCVAclintMTimerState,
> > num_harts, 0,
> > vmstate_info_uint64, uint64_t),
> > + VMSTATE_TIMER_PTR_VARRAY(timers, RISCVAclintMTimerState,
> > + num_harts),
> > VMSTATE_END_OF_LIST()
> > }
> > };
> > diff --git a/include/migration/vmstate.h b/include/migration/vmstate.h
> > index 1ff7bd9ac425ba67cd5ca7ad97bcf570f9e19abe..255e403e5a103188712425d95a719d181e1a7202 100644
> > --- a/include/migration/vmstate.h
> > +++ b/include/migration/vmstate.h
> > @@ -522,6 +522,16 @@ extern const VMStateInfo vmstate_info_qlist;
> > .offset = vmstate_offset_array(_s, _f, _type*, _n), \
> > }
> > +#define VMSTATE_VARRAY_OF_POINTER_UINT32(_field, _state, _field_num, _version, _info, _type) { \
> > + .name = (stringify(_field)), \
> > + .version_id = (_version), \
> > + .num_offset = vmstate_offset_value(_state, _field_num, uint32_t), \
> > + .info = &(_info), \
> > + .size = sizeof(_type), \
> > + .flags = VMS_VARRAY_UINT32 | VMS_ARRAY_OF_POINTER | VMS_POINTER, \
> > + .offset = vmstate_offset_pointer(_state, _field, _type), \
> > +}
> > +
> > #define VMSTATE_STRUCT_SUB_ARRAY(_field, _state, _start, _num, _version, _vmsd, _type) { \
> > .name = (stringify(_field)), \
> > .version_id = (_version), \
> > @@ -1035,6 +1045,10 @@ extern const VMStateInfo vmstate_info_qlist;
> > #define VMSTATE_TIMER_PTR_ARRAY(_f, _s, _n) \
> > VMSTATE_ARRAY_OF_POINTER(_f, _s, _n, 0, vmstate_info_timer, QEMUTimer *)
> > +#define VMSTATE_TIMER_PTR_VARRAY(_f, _s, _f_n) \
> > +VMSTATE_VARRAY_OF_POINTER_UINT32(_f, _s, _f_n, 0, vmstate_info_timer, \
> > + QEMUTimer *)
> > +
> > #define VMSTATE_TIMER_TEST(_f, _s, _test) \
> > VMSTATE_SINGLE_TEST(_f, _s, _test, 0, vmstate_info_timer, QEMUTimer)
> >
>
--
Peter Xu
next prev parent reply other threads:[~2025-09-09 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 9:46 [PATCH 0/3] Fix RISC-V timer migration issues TANG Tiancheng
2025-09-09 9:46 ` [PATCH 1/3] hw/intc: Save time_delta in RISC-V mtimer VMState TANG Tiancheng
2025-09-09 12:36 ` Daniel Henrique Barboza
2025-09-09 9:46 ` [PATCH 2/3] hw/intc: Save timers array " TANG Tiancheng
2025-09-09 12:45 ` Daniel Henrique Barboza
2025-09-09 21:34 ` Peter Xu [this message]
2025-09-10 1:33 ` LIU Zhiwei
2025-09-09 9:46 ` [PATCH 3/3] target/riscv: Save stimer and vstimer in CPU vmstate TANG Tiancheng
2025-09-09 12:49 ` Daniel Henrique Barboza
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aMCdYUZyQWQ4Qc4v@x1.local \
--to=peterx@redhat.com \
--cc=alistair.francis@wdc.com \
--cc=dbarboza@ventanamicro.com \
--cc=farosas@suse.de \
--cc=liwei1518@gmail.com \
--cc=lyndra@linux.alibaba.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).