linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
	Palmer Dabbelt <palmer@sifive.com>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Radim K <rkrcmar@redhat.com>, Anup Patel <anup@brainfault.org>,
	Anup Patel <Anup.Patel@wdc.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Christoph Hellwig <hch@infradead.org>,
	Atish Patra <Atish.Patra@wdc.com>,
	Alistair Francis <Alistair.Francis@wdc.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v4 00/20] KVM RISC-V Support
Date: Thu, 8 Aug 2019 10:54:43 +0200	[thread overview]
Message-ID: <df0638d9-e2f4-30f5-5400-9078bf9d1f99@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1908071606560.13971@viisi.sifive.com>

On 08/08/19 01:15, Paul Walmsley wrote:
> On Wed, 7 Aug 2019, Paolo Bonzini wrote:
> 
>> On 07/08/19 14:27, Anup Patel wrote:
>>> This series adds initial KVM RISC-V support. Currently, we are able to boot
>>> RISC-V 64bit Linux Guests with multiple VCPUs.
>>
>> Looks good to me!  Still need an Acked-by from arch/riscv folks if I
>> have to merge it, otherwise they can take care of the initial merge.
> 
> Since almost all of the patches touch arch/riscv files, we'll plan to 
> merge them through the RISC-V tree.  Care to ack patch one, and send tags 
> for any other patches as you think might be appropriate?

Patch 1, 3-20:

Acked-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>

In your 5.4 pull requests, it's best if you add a note that all RISC-V
KVM patches were acked and reviewed by me.  I'll also include a shoutout
about RISC-V KVM in my own pull request.

However, for Linux releases after 5.4 I would rather get pull requests
for arch/riscv/kvm from Anup and Atish without involving the RISC-V
tree.  Of course, they or I will ask for your ack, or for a topic
branch, on the occasion that something touches files outside their
maintainership area.  This is how things are already being handled for
ARM, POWER and s390 and it allows me to handle conflicts in common KVM
files before they reach Linus; these are more common than conflicts in
arch files.  If you have further questions on git and maintenance
workflows, just ask!

Paolo

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-08-08  8:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07 12:27 [PATCH v4 00/20] KVM RISC-V Support Anup Patel
2019-08-07 12:28 ` [PATCH v4 01/20] KVM: RISC-V: Add KVM_REG_RISCV for ONE_REG interface Anup Patel
2019-08-07 12:28 ` [PATCH v4 02/20] RISC-V: Add bitmap reprensenting ISA features common across CPUs Anup Patel
2019-08-07 18:47   ` Atish Patra
2019-08-08  4:03     ` Anup Patel
2019-08-07 12:28 ` [PATCH v4 03/20] RISC-V: Export few kernel symbols Anup Patel
2019-08-07 12:28 ` [PATCH v4 04/20] RISC-V: Add hypervisor extension related CSR defines Anup Patel
2019-08-07 12:28 ` [PATCH v4 05/20] RISC-V: Add initial skeletal KVM support Anup Patel
2019-08-07 12:28 ` [PATCH v4 06/20] RISC-V: KVM: Implement VCPU create, init and destroy functions Anup Patel
2019-08-07 12:28 ` [PATCH v4 07/20] RISC-V: KVM: Implement VCPU interrupts and requests handling Anup Patel
2019-08-07 12:28 ` [PATCH v4 08/20] RISC-V: KVM: Implement KVM_GET_ONE_REG/KVM_SET_ONE_REG ioctls Anup Patel
2019-08-07 12:28 ` [PATCH v4 09/20] RISC-V: KVM: Implement VCPU world-switch Anup Patel
2019-08-07 12:28 ` [PATCH v4 10/20] RISC-V: KVM: Handle MMIO exits for VCPU Anup Patel
2019-08-07 12:29 ` [PATCH v4 11/20] RISC-V: KVM: Handle WFI " Anup Patel
2019-08-07 12:29 ` [PATCH v4 12/20] RISC-V: KVM: Implement VMID allocator Anup Patel
2019-08-07 12:29 ` [PATCH v4 13/20] RISC-V: KVM: Implement stage2 page table programming Anup Patel
2019-08-07 12:29 ` [PATCH v4 14/20] RISC-V: KVM: Implement MMU notifiers Anup Patel
2019-08-07 12:29 ` [PATCH v4 15/20] RISC-V: KVM: Add timer functionality Anup Patel
2019-08-07 12:29 ` [PATCH v4 16/20] RISC-V: KVM: FP lazy save/restore Anup Patel
2019-08-07 12:29 ` [PATCH v4 17/20] RISC-V: KVM: Implement ONE REG interface for FP registers Anup Patel
2019-08-07 12:29 ` [PATCH v4 18/20] RISC-V: KVM: Add SBI v0.1 support Anup Patel
2019-08-07 12:29 ` [PATCH v4 19/20] RISC-V: Enable VIRTIO drivers in RV64 and RV32 defconfig Anup Patel
2019-08-07 12:29 ` [PATCH v4 20/20] RISC-V: KVM: Add MAINTAINERS entry Anup Patel
2019-08-07 20:09 ` [PATCH v4 00/20] KVM RISC-V Support Paolo Bonzini
2019-08-07 23:15   ` Paul Walmsley
2019-08-08  8:54     ` Paolo Bonzini [this message]
2019-08-09  1:35       ` Paul Walmsley
2019-08-09  7:37         ` Paolo Bonzini
2019-08-09  8:22           ` Anup Patel
2019-08-09  9:00             ` Paolo Bonzini
2019-08-09  9:26               ` Anup Patel

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=df0638d9-e2f4-30f5-5400-9078bf9d1f99@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Alistair.Francis@wdc.com \
    --cc=Anup.Patel@wdc.com \
    --cc=Atish.Patra@wdc.com \
    --cc=Damien.LeMoal@wdc.com \
    --cc=anup@brainfault.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=hch@infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --cc=paul.walmsley@sifive.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    /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).