From: "Radim Krčmář" <rkrcmar@ventanamicro.com>
To: "Xie Bo" <xb@ultrarisc.com>, <qemu-devel@nongnu.org>
Cc: <ajones@ventanamicro.com>, <qemu-riscv@nongnu.org>,
<alistair23@gmail.com>, <pbonzini@redhat.com>,
<anup@brainfault.org>, <alistair.francis@wdc.com>,
<palmer@dabbelt.com>, <xiamy@ultrarisc.com>,
<qemu-riscv-bounces+qemu-riscv=archiver.kernel.org@nongnu.org>
Subject: Re: [PATCH v9 2/2] Fix VM resume after QEMU+KVM migration
Date: Tue, 16 Sep 2025 10:03:46 +0200 [thread overview]
Message-ID: <DCU2H0SG4WG0.10TIXQISFI07A@ventanamicro.com> (raw)
In-Reply-To: <20250915070811.3422578-3-xb@ultrarisc.com>
2025-09-15T15:08:08+08:00, Xie Bo <xb@ultrarisc.com>:
> Fix two migration issues for virtual machines in KVM mode:
> 1.It saves and restores the vCPU's privilege mode to ensure that the
> vCPU's privilege mode is correct after migration.
> 2.It saves and restores the vCPU's mp_state (runnable or stopped) and
> includes this state in the migration sequence, upgrading the vmstate
> version to ensure that the vCPU's mp_state is correct after migration.
This could be two patches, each doing just one thing:
* fix mode
* fix mp_state
And the mode hunk that I pointed out in [v9 1/2] could be put in the
patch that fixes mode.
I jumped quite late into the review, so if others are fine with the
current split,
Reviewed-by: Radim Krčmář <rkrcmar@ventanamicro.com>
next prev parent reply other threads:[~2025-09-16 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 7:08 [PATCH v9 0/2] target/riscv：Fix riscv64 kvm migration Xie Bo
2025-09-15 7:08 ` [PATCH v9 1/2] Set KVM initial privilege mode and mp_state Xie Bo
2025-09-16 8:00 ` Radim Krčmář
2025-09-29 1:48 ` Alistair Francis
2025-09-29 17:36 ` Radim Krčmář
2025-10-22 11:47 ` Daniel Henrique Barboza
2025-09-15 7:08 ` [PATCH v9 2/2] Fix VM resume after QEMU+KVM migration Xie Bo
2025-09-16 8:03 ` Radim Krčmář [this message]
2025-09-15 15:31 ` [PATCH v9 0/2] target/riscv：Fix riscv64 kvm migration Andrew Jones
2025-09-29 1:43 ` 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=DCU2H0SG4WG0.10TIXQISFI07A@ventanamicro.com \
--to=rkrcmar@ventanamicro.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=anup@brainfault.org \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv-bounces+qemu-riscv=archiver.kernel.org@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=xb@ultrarisc.com \
--cc=xiamy@ultrarisc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.