From: Paolo Bonzini <pbonzini@redhat.com>
To: Anup Patel <anup@brainfault.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Atish Patra <atishp@atishpatra.org>,
KVM General <kvm@vger.kernel.org>,
kvm-riscv@lists.infradead.org,
linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] KVM/riscv changes for 5.18
Date: Tue, 15 Mar 2022 22:21:39 +0100 [thread overview]
Message-ID: <47f64c5e-fa36-9e87-763b-4e7385713e76@redhat.com> (raw)
In-Reply-To: <CAAhSdy1cBkGqBLN7iZY-FUx2BFGoXmxd4WZJemPSRKz6my8cZQ@mail.gmail.com>
On 3/11/22 18:02, Anup Patel wrote:
> Hi Paolo,
>
> We have three KVM RISC-V changes for 5.18 which are:
> 1) Prevent KVM_COMPAT from being selected
> 2) Refine __kvm_riscv_switch_to() implementation
> 3) RISC-V SBI v0.3 support
>
> I don't expect any other KVM RISC-V changes for 5.18.
>
> Please pull.
>
> Regards,
> Anup
>
> The following changes since commit 4a204f7895878363ca8211f50ec610408c8c70aa:
>
> KVM: SVM: Allow AVIC support on system w/ physical APIC ID > 255
> (2022-03-08 10:59:12 -0500)
>
> are available in the Git repository at:
>
> https://github.com/kvm-riscv/linux.git tags/kvm-riscv-5.18-1
>
> for you to fetch changes up to 763c8bed8c05ffcce8cba882e69cd6b03df07019:
>
> RISC-V: KVM: Implement SBI HSM suspend call (2022-03-11 19:02:39 +0530)
>
> ----------------------------------------------------------------
> KVM/riscv changes for 5.18
>
> - Prevent KVM_COMPAT from being selected
> - Refine __kvm_riscv_switch_to() implementation
> - RISC-V SBI v0.3 support
Pulled, thanks.
Paolo
>
> ----------------------------------------------------------------
> Anup Patel (6):
> RISC-V: KVM: Upgrade SBI spec version to v0.3
> RISC-V: KVM: Add common kvm_riscv_vcpu_sbi_system_reset() function
> RISC-V: KVM: Implement SBI v0.3 SRST extension
> RISC-V: Add SBI HSM suspend related defines
> RISC-V: KVM: Add common kvm_riscv_vcpu_wfi() function
> RISC-V: KVM: Implement SBI HSM suspend call
>
> Guo Ren (1):
> KVM: compat: riscv: Prevent KVM_COMPAT from being selected
>
> Vincent Chen (1):
> RISC-V: KVM: Refine __kvm_riscv_switch_to() implementation
>
> Yang Li (1):
> RISC-V: KVM: remove unneeded semicolon
>
> arch/riscv/include/asm/kvm_host.h | 1 +
> arch/riscv/include/asm/kvm_vcpu_sbi.h | 5 ++-
> arch/riscv/include/asm/sbi.h | 27 +++++++++++++---
> arch/riscv/kernel/cpu_ops_sbi.c | 2 +-
> arch/riscv/kvm/vcpu_exit.c | 22 +++++++++----
> arch/riscv/kvm/vcpu_sbi.c | 19 +++++++++++
> arch/riscv/kvm/vcpu_sbi_hsm.c | 18 +++++++++--
> arch/riscv/kvm/vcpu_sbi_replace.c | 44 +++++++++++++++++++++++++
> arch/riscv/kvm/vcpu_sbi_v01.c | 20 ++----------
> arch/riscv/kvm/vcpu_switch.S | 60 ++++++++++++++++++++---------------
> virt/kvm/Kconfig | 2 +-
> 11 files changed, 161 insertions(+), 59 deletions(-)
>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2022-03-15 21:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 17:02 [GIT PULL] KVM/riscv changes for 5.18 Anup Patel
2022-03-15 21:21 ` Paolo Bonzini [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=47f64c5e-fa36-9e87-763b-4e7385713e76@redhat.com \
--to=pbonzini@redhat.com \
--cc=anup@brainfault.org \
--cc=atishp@atishpatra.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.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