From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-11.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 50AA9C433ED for ; Wed, 19 May 2021 04:58:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 24E8A613AC for ; Wed, 19 May 2021 04:58:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238323AbhESE7e (ORCPT ); Wed, 19 May 2021 00:59:34 -0400 Received: from mail.kernel.org ([198.145.29.99]:50246 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229939AbhESE7d (ORCPT ); Wed, 19 May 2021 00:59:33 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6560561355; Wed, 19 May 2021 04:58:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1621400294; bh=sBPi7doTjepZo5AoeX6D/DqrfoxCCmiTbbDfO6A7+1A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Tg2fxanYYVeqmsedHZTVahMC53Je13j2qQo6irCgVnD9l6R8hP1VifEKRUxwM2YPf WFdvYQcpyQF7Ff73XO1FgRGZR0+AftflNxfwNilci58q/w6E1SwydNRY6uwOxzMEyF 6t74rsmccXGRBh0DVv57nMWSBPWKBOO0ZMymaVQc= Date: Wed, 19 May 2021 06:58:11 +0200 From: Greg Kroah-Hartman To: Anup Patel Cc: Palmer Dabbelt , Palmer Dabbelt , Paul Walmsley , Albert Ou , Paolo Bonzini , Jonathan Corbet , Alexander Graf , Atish Patra , Alistair Francis , Damien Le Moal , Anup Patel , kvm@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev Subject: Re: [PATCH v18 00/18] KVM RISC-V Support Message-ID: References: <20210519033553.1110536-1-anup.patel@wdc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210519033553.1110536-1-anup.patel@wdc.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Wed, May 19, 2021 at 09:05:35AM +0530, Anup Patel wrote: > From: Anup Patel > > This series adds initial KVM RISC-V support. Currently, we are able to boot > Linux on RV64/RV32 Guest with multiple VCPUs. > > Key aspects of KVM RISC-V added by this series are: > 1. No RISC-V specific KVM IOCTL > 2. Minimal possible KVM world-switch which touches only GPRs and few CSRs > 3. Both RV64 and RV32 host supported > 4. Full Guest/VM switch is done via vcpu_get/vcpu_put infrastructure > 5. KVM ONE_REG interface for VCPU register access from user-space > 6. PLIC emulation is done in user-space > 7. Timer and IPI emuation is done in-kernel > 8. Both Sv39x4 and Sv48x4 supported for RV64 host > 9. MMU notifiers supported > 10. Generic dirtylog supported > 11. FP lazy save/restore supported > 12. SBI v0.1 emulation for KVM Guest available > 13. Forward unhandled SBI calls to KVM userspace > 14. Hugepage support for Guest/VM > 15. IOEVENTFD support for Vhost > > Here's a brief TODO list which we will work upon after this series: > 1. SBI v0.2 emulation in-kernel > 2. SBI v0.2 hart state management emulation in-kernel > 3. In-kernel PLIC emulation > 4. ..... and more ..... > > This series can be found in riscv_kvm_v18 branch at: > https//github.com/avpatel/linux.git > > Our work-in-progress KVMTOOL RISC-V port can be found in riscv_v7 branch > at: https//github.com/avpatel/kvmtool.git > > The QEMU RISC-V hypervisor emulation is done by Alistair and is available > in master branch at: https://git.qemu.org/git/qemu.git > > To play around with KVM RISC-V, refer KVM RISC-V wiki at: > https://github.com/kvm-riscv/howto/wiki > https://github.com/kvm-riscv/howto/wiki/KVM-RISCV64-on-QEMU > https://github.com/kvm-riscv/howto/wiki/KVM-RISCV64-on-Spike > > Changes since v17: > - Rebased on Linux-5.13-rc2 > - Moved to new KVM MMU notifier APIs > - Removed redundant kvm_arch_vcpu_uninit() > - Moved KVM RISC-V sources to drivers/staging for compliance with > Linux RISC-V patch acceptance policy What is this new "patch acceptance policy" and what does it have to do with drivers/staging? What does drivers/staging/ have to do with this at all? Did anyone ask the staging maintainer about this? Not cool, and not something I'm about to take without some very good reasons... greg k-h