kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Will Deacon <will@kernel.org>
To: Anup Patel <Anup.Patel@wdc.com>
Cc: Will Deacon <will.deacon@arm.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Atish Patra <Atish.Patra@wdc.com>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	Anup Patel <anup@brainfault.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"kvm-riscv@lists.infradead.org" <kvm-riscv@lists.infradead.org>,
	palmer@dabbelt.com
Subject: Re: [kvmtool RFC PATCH v2 0/8] KVMTOOL RISC-V support
Date: Wed, 5 Feb 2020 17:13:34 +0000	[thread overview]
Message-ID: <20200205171334.GB908@willie-the-truck> (raw)
In-Reply-To: <20200127123527.106825-1-anup.patel@wdc.com>

On Mon, Jan 27, 2020 at 12:35:55PM +0000, Anup Patel wrote:
> This series adds RISC-V support for KVMTOOL and it is based on
> the v10 of KVM RISC-V series. The KVM RISC-V patches are not yet
> merged in Linux kernel but it will be good to get early review
> for KVMTOOL RISC-V support.
> 
> The KVMTOOL RISC-V patches can be found in riscv_master branch at:
> https//github.com/kvm-riscv/kvmtool.git
> 
> The KVM RISC-V patches can be found in riscv_kvm_master branch at:
> https//github.com/kvm-riscv/linux.git
> 
> The QEMU RISC-V hypervisor emulation is done by Alistair and is
> available in mainline/alistair/riscv-hyp-ext-v0.5.1 branch at:
> https://github.com/kvm-riscv/qemu.git
> 
> Changes since v1:
>  - Use linux/sizes.h in kvm/kvm-arch.h
>  - Added comment in kvm/kvm-arch.h about why PCI config space is 256M
>  - Remove forward declaration of "struct kvm" from kvm/kvm-cpu-arch.h
>  - Fixed placement of DTB and INITRD in guest RAM
>  - Use __riscv_xlen instead of sizeof(unsigned long) in __kvm_reg_id()

I don't know anything about the RISC-V virtualisation architecture, so
I've added Palmer to cc in case he can review this and/or suggest somebody
else who can.

Will

      parent reply	other threads:[~2020-02-05 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 12:35 [kvmtool RFC PATCH v2 0/8] KVMTOOL RISC-V support Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 1/8] update_headers: Sync-up ABI headers with Linux-5.5-rc3 Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 2/8] riscv: Initial skeletal support Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 3/8] riscv: Implement Guest/VM arch functions Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 4/8] riscv: Implement Guest/VM VCPU " Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 5/8] riscv: Add PLIC device emulation Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 6/8] riscv: Generate FDT at runtime for Guest/VM Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 7/8] riscv: Handle SBI calls forwarded to user space Anup Patel
2020-01-27 12:36 ` [kvmtool RFC PATCH v2 8/8] riscv: Generate PCI host DT node Anup Patel
2020-02-05 17:13 ` Will Deacon [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=20200205171334.GB908@willie-the-truck \
    --to=will@kernel.org \
    --cc=Alistair.Francis@wdc.com \
    --cc=Anup.Patel@wdc.com \
    --cc=Atish.Patra@wdc.com \
    --cc=anup@brainfault.org \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=will.deacon@arm.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).