From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: seanjc@google.com, Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH v2] MAINTAINERS: Reorganize KVM/x86 maintainership
Date: Thu, 23 Jun 2022 16:50:01 +0200 [thread overview]
Message-ID: <87tu8bwi1y.fsf@redhat.com> (raw)
In-Reply-To: <20220623143059.2626661-1-pbonzini@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> For the last few years I have been the sole maintainer of KVM, albeit
> getting serious help from all the people who have reviewed hundreds of
> patches. The volume of KVM x86 alone has gotten to the point where one
> maintainer is not enough; especially if that maintainer is not doing it
> full time and if they want to keep up with the evolution of ARM64 and
> RISC-V at both the architecture and the hypervisor level.
>
> So, this patch is the first step in restoring double maintainership
> or even transitioning to the submaintainer model of other architectures.
>
> The changes here were mostly proposed by Sean offlist and they are twofold:
>
> - revisiting the set of KVM x86 reviewers. It's important to have an
> an accurate list of people that are actively reviewing patches ("R"),
> as well as people that are able to act on bug reports ("M"). Otherwise,
> voids to be filled are not easily visible. The proposal is to split
> KVM on Hyper-V, which is where Vitaly has been the main contributor
> for quite some time now; likewise for KVM paravirt support, which
> has been the main interest of Wanpeng and to which Vitaly has also
> contributed (e.g., for async page faults). Jim and Joerg have not been
> particularly active (though Joerg has worked on guest support for AMD
> SEV); knowing them a bit, I can't imagine they would object to their
> removal or even be surprised, but please speak up if you do.
>
> - promoting Sean to maintainer for KVM x86 host support. While for
> now this changes little, let's treat it as a harbinger for future
> changes. The plan is that I would keep the final integration testing
> for quite some time, and probably focus more on -rc work. This will
> give me more time to clean up my ad hoc setup and moving towards a
> more public CI, with Sean focusing instead on next-release patches,
> and the testing up to where kvm-unit-tests and selftests pass. In
> order to facilitate collaboration between Sean and myself, we'll
> also formalize a bit more the various branches of kvm.git.
>
> Nothing is going to change with respect to handling pull requests to Linus
> and from other architectures, as well as maintainance of the generic code
> (which I expect and hope to be more important as architectures try to
> share more code) and documentation. However, it's not a coincidence
> that my entry is now the last for x86, ready to be demoted to reviewer
> if/when the right time comes.
>
> Suggested-by: Sean Christopherson <seanjc@google.com>
> Co-developed-by: Sean Christopherson <seanjc@google.com>
> Cc: kvm@vger.kernel.org
> Cc: Sean Christopherson <seanjc@google.com>
> Cc: Vitaly Kuznetsov <vkuznets@redhat.com>
> Cc: Wanpeng Li <wanpengli@tencent.com>
> Cc: Jim Mattson <jmattson@google.com>
> Cc: Joerg Roedel <joro@8bytes.org>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> MAINTAINERS | 40 +++++++++++++++++++++++++++++++---------
> 1 file changed, 31 insertions(+), 9 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 97014ae3e5ed..968b622bc3ce 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -10897,28 +10897,50 @@ F: tools/testing/selftests/kvm/*/s390x/
> F: tools/testing/selftests/kvm/s390x/
>
> KERNEL VIRTUAL MACHINE FOR X86 (KVM/x86)
> +M: Sean Christopherson <seanjc@google.com>
> M: Paolo Bonzini <pbonzini@redhat.com>
> -R: Sean Christopherson <seanjc@google.com>
> -R: Vitaly Kuznetsov <vkuznets@redhat.com>
> -R: Wanpeng Li <wanpengli@tencent.com>
> -R: Jim Mattson <jmattson@google.com>
> -R: Joerg Roedel <joro@8bytes.org>
> L: kvm@vger.kernel.org
> S: Supported
> -W: http://www.linux-kvm.org
> T: git git://git.kernel.org/pub/scm/virt/kvm/kvm.git
> F: arch/x86/include/asm/kvm*
> -F: arch/x86/include/asm/pvclock-abi.h
> F: arch/x86/include/asm/svm.h
> F: arch/x86/include/asm/vmx*.h
> F: arch/x86/include/uapi/asm/kvm*
> F: arch/x86/include/uapi/asm/svm.h
> F: arch/x86/include/uapi/asm/vmx.h
> -F: arch/x86/kernel/kvm.c
> -F: arch/x86/kernel/kvmclock.c
> F: arch/x86/kvm/
> F: arch/x86/kvm/*/
>
> +KVM PARAVIRT (KVM/paravirt)
> +M: Paolo Bonzini <pbonzini@redhat.com>
> +R: Wanpeng Li <wanpengli@tencent.com>
> +R: Vitaly Kuznetsov <vkuznets@redhat.com>
> +L: kvm@vger.kernel.org
> +S: Supported
> +T: git git://git.kernel.org/pub/scm/virt/kvm/kvm.git
> +F: arch/x86/kernel/kvm.c
> +F: arch/x86/kernel/kvmclock.c
> +F: arch/x86/include/asm/pvclock-abi.h
> +F: include/linux/kvm_para.h
> +F: include/uapi/linux/kvm_para.h
> +F: include/uapi/asm-generic/kvm_para.h
> +F: include/asm-generic/kvm_para.h
> +F: arch/um/include/asm/kvm_para.h
> +F: arch/x86/include/asm/kvm_para.h
> +F: arch/x86/include/uapi/asm/kvm_para.h
> +
> +KVM X86 HYPER-V (KVM/hyper-v)
> +M: Vitaly Kuznetsov <vkuznets@redhat.com>
> +M: Sean Christopherson <seanjc@google.com>
> +M: Paolo Bonzini <pbonzini@redhat.com>
> +L: kvm@vger.kernel.org
> +S: Supported
> +T: git git://git.kernel.org/pub/scm/virt/kvm/kvm.git
> +F: arch/x86/kvm/hyperv.*
> +F: arch/x86/kvm/kvm_onhyperv.*
> +F: arch/x86/kvm/svm/svm_onhyperv.*
"arch/x86/kvm/svm/hyperv.*" is still missing) LGTM otherwise, and as it
has my name:
Acked-by: Vitaly Kuznetsov <vkuznets@redhat.com>
> +F: arch/x86/kvm/vmx/evmcs.*
> +
> KERNFS
> M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> M: Tejun Heo <tj@kernel.org>
--
Vitaly
next prev parent reply other threads:[~2022-06-23 14:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 14:30 [PATCH v2] MAINTAINERS: Reorganize KVM/x86 maintainership Paolo Bonzini
2022-06-23 14:50 ` Vitaly Kuznetsov [this message]
2022-06-24 1:46 ` Wanpeng Li
2022-06-24 2:11 ` Wanpeng Li
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=87tu8bwi1y.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=wanpengli@tencent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.