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
Subject: Re: [PATCH v2] KVM: MAINTAINERS: note that linux-kvm.org isn't current
Date: Tue, 13 Jun 2023 14:58:16 -0700 [thread overview]
Message-ID: <ZIjmeC4binNWlYoi@google.com> (raw)
In-Reply-To: <b75c9696-9abb-7a3f-0fb2-56af8ef21bb6@redhat.com>
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.
prev parent reply other threads:[~2023-06-13 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 15:32 [PATCH v2] KVM: MAINTAINERS: note that linux-kvm.org isn't current Randy Dunlap
2023-05-30 23:39 ` Randy Dunlap
2023-06-03 1:07 ` Sean Christopherson
2023-06-03 2:27 ` Randy Dunlap
2023-06-05 16:48 ` Paolo Bonzini
2023-06-13 21:58 ` Sean Christopherson [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=ZIjmeC4binNWlYoi@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rdunlap@infradead.org \
/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.