From: Alistair Francis <alistair23@gmail.com>
To: Xie Bo <xb@ultrarisc.com>
Cc: qemu-devel@nongnu.org, ajones@ventanamicro.com,
qemu-riscv@nongnu.org, pbonzini@redhat.com, anup@brainfault.org,
alistair.francis@wdc.com, rkrcmar@ventanamicro.com,
palmer@dabbelt.com, xiamy@ultrarisc.com
Subject: Re: [PATCH v9 0/2] target/riscv:Fix riscv64 kvm migration
Date: Mon, 29 Sep 2025 11:43:18 +1000 [thread overview]
Message-ID: <CAKmqyKOnJcFbZCCfssQYpBS5VwPZJ3_28TxLvkMWD8nukFD6uw@mail.gmail.com> (raw)
In-Reply-To: <20250915070811.3422578-1-xb@ultrarisc.com>
On Mon, Sep 15, 2025 at 5:08 PM Xie Bo <xb@ultrarisc.com> wrote:
>
> This is v9 of the series. Compared to v8, the patches are now based on
> the 'riscv-to-apply.next' branch from Alistair's repository:
>
> https://github.com/alistair23/qemu/tree/riscv-to-apply.next
>
> Changes since v8:
> - Rebased the series onto [alistair/riscv-to-apply.next]
> - Removed the previous 'Reviewed-by' tags due to the rebase
> * The changes are purely mechanical; no code logic was altered *
> - Added 'Cc: qemu-stable@nongnu.org'
>
> Xie Bo (2):
> Set KVM initial privilege mode and mp_state
> Fix VM resume after QEMU+KVM migration
Thanks!
Applied to riscv-to-apply.next
Alistair
>
> target/riscv/cpu.c | 17 +++++++++-
> target/riscv/cpu.h | 2 ++
> target/riscv/kvm/kvm-cpu.c | 60 ++++++++++++++++++++++++++++--------
> target/riscv/kvm/kvm_riscv.h | 3 +-
> target/riscv/machine.c | 5 +--
> 5 files changed, 70 insertions(+), 17 deletions(-)
>
> --
> 2.43.0
>
prev parent reply other threads:[~2025-09-29 1:45 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ář
2025-09-15 15:31 ` [PATCH v9 0/2] target/riscv:Fix riscv64 kvm migration Andrew Jones
2025-09-29 1:43 ` Alistair Francis [this message]
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=CAKmqyKOnJcFbZCCfssQYpBS5VwPZJ3_28TxLvkMWD8nukFD6uw@mail.gmail.com \
--to=alistair23@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=alistair.francis@wdc.com \
--cc=anup@brainfault.org \
--cc=palmer@dabbelt.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=rkrcmar@ventanamicro.com \
--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 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).