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(-)
This series(v8) replaces the earlier series patch"[PATCH v7 for v10.0.0 0/2] target/riscv: Fix riscv64 kvm migration". Changes since v7: - Patch 1: unchanged; keep Reviewed-by from Andrew Jones <ajones@ventanamicro.com> - Patch 2: add Reviewed-by from Andrew Jones <ajones@ventanamicro.com> - No other changes (code is the same as v7) Xie Bo (2): Set KVM initial privilege mode and mp_state Fix VM resume after QEMU+KVM migration 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
On 12.09.2025 11:55, Xie Bo wrote: > This series(v8) replaces the earlier series patch"[PATCH v7 for v10.0.0 0/2] > target/riscv: Fix riscv64 kvm migration". Ping? Can we apply this to the master branch, so I can pick it up for the stable series? Thanks, /mjt
Hi Michael， we are planned to have a regular RVI sig-hypervisor meeting on the 30th, with Radim and Andrew. A conclusive email will be sent shortly after. Thanks for the reminder. Regards， Xie Bo > -----原始邮件----- > 发件人: "Michael Tokarev" <mjt@tls.msk.ru> > 发送时间:2025-09-27 21:57:06 (星期六) > 收件人: "Xie Bo" <xb@ultrarisc.com>, 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 > 主题: Re: [PATCH v8 for v10.0.0 0/2] target/riscv：Fix riscv64 kvm migration > > On 12.09.2025 11:55, Xie Bo wrote: > > This series(v8) replaces the earlier series patch"[PATCH v7 for v10.0.0 0/2] > > target/riscv: Fix riscv64 kvm migration". > > Ping? Can we apply this to the master branch, so I can pick it up > for the stable series? > > Thanks, > > /mjt ______________________www.ultrarisc.com 重要提示：本邮件包括附件的内容是受法律保护的保密信息，如果您不是指定收件人，请立即将本邮件删除，法律禁止任何非法的披露、复制、传播或以任何方式使用本邮件。本邮件中包含的意见、建议是基于或受到我方表达和定义的条款及条件的限定，如无我方的正式书面澄清或授权，不可被单独作为任何情形下的证据或依据。感谢您的理解与配合。版权所有。IMPORTANT NOTICE: This email, including its attachment if any, is confidential. If you are not the intended recipient, please delete it from your computer immediately. Any disclosure, copying, or distribution of this message, or taking of any action based on it is strictly prohibited. Any opinions and suggestions contained in this email are subject to the terms and conditions expressed and defined by us and should not be relied upon unconditionally under any circumstances unless they are confirmed in official written clarification or authorization from us. Thank you for your understanding and cooperation.All rights reserved.
On Fri, Sep 12, 2025 at 6:56 PM Xie Bo <xb@ultrarisc.com> wrote: > > This series(v8) replaces the earlier series patch"[PATCH v7 for v10.0.0 0/2] > target/riscv: Fix riscv64 kvm migration". > > Changes since v7: > - Patch 1: unchanged; keep Reviewed-by from Andrew Jones <ajones@ventanamicro.com> > - Patch 2: add Reviewed-by from Andrew Jones <ajones@ventanamicro.com> > - No other changes (code is the same as v7) > > Xie Bo (2): > Set KVM initial privilege mode and mp_state > Fix VM resume after QEMU+KVM migration Can you add the following tag: Cc: qemu-stable@nongnu.org to each commit message. That way it will be picked up for stable. Can you also rebase the series on: https://github.com/alistair23/qemu/tree/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 > >
On 15.09.2025 08:06, Alistair Francis wrote: .. > Can you add the following tag: > > Cc: qemu-stable@nongnu.org > > to each commit message. That way it will be picked up for stable. Hi! This is just so I'm aware of the commits. Here, they're already on my radar, so there's no need to change anything :) Thanks, /mjt
© 2016 - 2025 Red Hat, Inc.