From: Alistair Francis <alistair23@gmail.com>
To: TANG Tiancheng <lyndra@linux.alibaba.com>
Cc: qemu-devel@nongnu.org, Palmer Dabbelt <palmer@dabbelt.com>,
Alistair Francis <alistair.francis@wdc.com>,
Weiwei Li <liwei1518@gmail.com>,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
qemu-riscv@nongnu.org, Peter Xu <peterx@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: Re: [PATCH v3 0/4] Fix RISC-V timer migration issues
Date: Mon, 15 Sep 2025 14:25:45 +1000 [thread overview]
Message-ID: <CAKmqyKM2Pm-_pci0uany7cNmwCUf8UXNA6K24UYRDta29fDv=g@mail.gmail.com> (raw)
In-Reply-To: <20250911-timers-v3-0-60508f640050@linux.alibaba.com>
On Thu, Sep 11, 2025 at 7:59 PM TANG Tiancheng <lyndra@linux.alibaba.com> wrote:
>
> This patch set fixes several timer-related migration issues in QEMU's
> RISC-V implementation that cause timer events to be lost or behave
> incorrectly after snapshot save/restore or live migration.
>
> The problems addressed are:
>
> 1. ACLINT mtimer time_delta not migrated: The time_delta field in
> RISCVAclintMTimerState was missing from vmstate, causing incorrect
> mtime values after snapshot restore. This resulted in guest time
> appearing "frozen" until enough virtual time elapsed to compensate
> for the offset error.
>
> 2. ACLINT mtimer timers array not migrated: Active timer events
> scheduled via riscv_aclint_mtimer_write_timecmp() were not being
> migrated, causing pending timer interrupts to be lost after restore.
>
> 3. CPU stimer/vstimer not migrated: The S-mode and VS-mode timer
> pointers in CPURISCVState were missing from vmstate_riscv_cpu,
> causing supervisor-level timer events to be lost.
>
> The patch set introduces a new VMSTATE_TIMER_PTR_VARRAY macro to handle
> migration of variable-length timer pointer arrays, and adds the missing
> timer fields to the appropriate vmstate structures.
>
> Signed-off-by: TANG Tiancheng <lyndra@linux.alibaba.com>
Thanks!
Applied to riscv-to-apply.next
Alistair
> ---
> Changes in v3:
> - Remove 'include/' of the subject at patch v2 2/4.
> - Added Reviewed-by from Peter Xu.
> - Link to v2: https://lore.kernel.org/qemu-devel/20250910-timers-v2-0-31359f1f6ee8@linux.alibaba.com
>
> Changes in v2:
> - Split VMSTATE_VARRAY_OF_POINTER_UINT32() into a separate patch,
> and define VMSTATE_TIMER_PTR_VARRAY() in riscv_aclint.h.
> - Added Reviewed-by from Daniel Henrique Barboza.
> - Link to v1: https://lore.kernel.org/qemu-devel/20250909-timers-v1-0-7ee18a9d8f4b@linux.alibaba.com
>
> ---
> TANG Tiancheng (4):
> hw/intc: Save time_delta in RISC-V mtimer VMState
> migration: Add support for a variable-length array of UINT32 pointers
> hw/intc: Save timers array in RISC-V mtimer VMState
> target/riscv: Save stimer and vstimer in CPU vmstate
>
> hw/intc/riscv_aclint.c | 7 +++++--
> include/hw/intc/riscv_aclint.h | 4 ++++
> include/migration/vmstate.h | 10 ++++++++++
> target/riscv/machine.c | 25 +++++++++++++++++++++++++
> 4 files changed, 44 insertions(+), 2 deletions(-)
> ---
> base-commit: 6a9fa5ef3230a7d51e0d953a59ee9ef10af705b8
> change-id: 20250909-timers-18c2c67b1a2a
>
> Best regards,
> --
> TANG Tiancheng <lyndra@linux.alibaba.com>
>
>
next prev parent reply other threads:[~2025-09-15 4:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 9:56 [PATCH v3 0/4] Fix RISC-V timer migration issues TANG Tiancheng
2025-09-11 9:56 ` [PATCH v3 1/4] hw/intc: Save time_delta in RISC-V mtimer VMState TANG Tiancheng
2025-09-15 4:15 ` Alistair Francis
2025-09-11 9:56 ` [PATCH v3 2/4] migration: Add support for a variable-length array of UINT32 pointers TANG Tiancheng
2025-09-15 4:16 ` Alistair Francis
2025-09-11 9:56 ` [PATCH v3 3/4] hw/intc: Save timers array in RISC-V mtimer VMState TANG Tiancheng
2025-09-15 4:20 ` Alistair Francis
2025-09-11 9:56 ` [PATCH v3 4/4] target/riscv: Save stimer and vstimer in CPU vmstate TANG Tiancheng
2025-09-15 4:21 ` Alistair Francis
2025-09-15 4:25 ` Alistair Francis [this message]
2025-10-04 7:16 ` [PATCH v3 0/4] Fix RISC-V timer migration issues Michael Tokarev
2025-10-09 2:35 ` Alistair Francis
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='CAKmqyKM2Pm-_pci0uany7cNmwCUf8UXNA6K24UYRDta29fDv=g@mail.gmail.com' \
--to=alistair23@gmail.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=peterx@redhat.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).