From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: Sean Christopherson <seanjc@google.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>
Subject: Re: [PATCH] MAINTAINERS: Reorganize KVM/x86 maintainership
Date: Thu, 23 Jun 2022 19:58:03 +0200 [thread overview]
Message-ID: <21ac5af2-6cb7-29a9-dcc5-467336951982@redhat.com> (raw)
In-Reply-To: <878rpny47v.fsf@redhat.com>
On 6/23/22 14:05, Vitaly Kuznetsov wrote:
>> +KVM PARAVIRT (KVM/paravirt)
>> +M: Paolo Bonzini <pbonzini@redhat.com>
>> +R: Wanpeng Li <wanpengli@tencent.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
>
> If we add Async PF to the 'KVM/paravirt' scope:
>
> +F: virt/kvm/async_pf.c
> and maybe even
> +F: arch/x86/kvm/x86.c
>
> then I can probably volunteer as a reviewer.
There is of course a host component to all paravirt infrastructure, the
idea was to have a separate part specifically for the guest side. It
tends to have its own set of issues (e.g. suspend/resume, 32-bit, etc.).
I will add you anyway as reviewer, it makes sense.
>> +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>
>
> Don't we also need:
>
> S: Supported
> L: kvm@vger.kernel.org
>
> here?
Yeah, especially the "S" (the list is caught by the generic KVM part).
Paolo
>> +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.*
>
> +F: arch/x86/kvm/svm/hyperv.*
>
>> +F: arch/x86/kvm/vmx/evmcs.*
>> +
>> KERNFS
>> M: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> M: Tejun Heo <tj@kernel.org>
>
prev parent reply other threads:[~2022-06-23 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 11:46 Paolo Bonzini
2022-06-23 12:05 ` Vitaly Kuznetsov
2022-06-23 17:58 ` 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=21ac5af2-6cb7-29a9-dcc5-467336951982@redhat.com \
--to=pbonzini@redhat.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®