Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 13 Jun 2023 14:58:16 -0700
In-Reply-To: <b75c9696-9abb-7a3f-0fb2-56af8ef21bb6@redhat.com>
Mime-Version: 1.0
References: <20230525153204.27960-1-rdunlap@infradead.org> <ZHqSYbYscprsU2qT@google.com>
 <b75c9696-9abb-7a3f-0fb2-56af8ef21bb6@redhat.com>
Message-ID: <ZIjmeC4binNWlYoi@google.com>
Subject: Re: [PATCH v2] KVM: MAINTAINERS: note that linux-kvm.org isn't current
From:   Sean Christopherson <seanjc@google.com>
To:     Paolo Bonzini <pbonzini@redhat.com>
Cc:     Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org,
        kvm@vger.kernel.org
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

On Mon, Jun 05, 2023, Paolo Bonzini wrote:
> On 6/3/23 03:07, Sean Christopherson wrote:
> > It's definitely stale, though unless Red Hat (presumed hoster) plans on decomissioning
> > the site, I'd prefer to keep the reference and instead improve the site.  We (Google)
> > are planning on committing resources to update KVM documentation that doesn't belong
> > in the kernel itself, and updatingwww.linux-kvm.org  instead of creating something new
> > seems like a no-brainer.  I can't promise an updates will happen super quickly, but I
> > will do what I can to make 'em happen sooner than later.
> 
> We don't plan to decommission the website (especially not the old KVM Forum
> content), though we might move it over to the same (container-based) setup
> as wiki.qemu.org.
> 
> What content do you have in mind that doesn't fit in the kernel
> Documentation/ tree?

Mostly developer focused stuff, e.g. using KVM to test/debug kernels and/or KVM
itself, using 9PFS to hoist modules from into a VM without having to install the
kernel in the guest image, in-depth walkthroughs of various code flows (e.g. how
KVM takes an EPT violation and turns that into a mapping), etc.