From: Sean Christopherson <seanjc@google.com>
To: Amy Parker <apark0006@student.cerritos.edu>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com
Subject: Re: Addition of a staging subdirectory to virt/ for in-development features
Date: Wed, 20 Oct 2021 23:11:47 +0000 [thread overview]
Message-ID: <YXCiM2iKZuiwnfjj@google.com> (raw)
In-Reply-To: <CAPOgqxEuo6VFAUWc5os6N1iPqh-mQrSg6d09Tj5vy82Gw=v-fg@mail.gmail.com>
On Wed, Oct 20, 2021, Amy Parker wrote:
> Hello all.
>
> Has the idea of having a staging subdirectory for KVM been proposed before?
Not that I know of.
> It could become a buffer place for KVM features currently in development/not
> production ready, but that should be able to be conditionally included into
> the kernel. With a staging directory, these features would be divorced from
> KVM mainline, but would be able to be rolled out promptly to users while they
> are being refined.
Can you give an example?
I'm struggling to envision a feature that is both large enough to warrant
"staging", yet isolated enough to actually be "divorced from KVM mainline".
One of the rules for staging/drivers is that the drivers are standalone and don't
require changes to the kernel proper outside of docs, firmware, and perhaps
exports.
next prev parent reply other threads:[~2021-10-20 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 22:28 Addition of a staging subdirectory to virt/ for in-development features Amy Parker
2021-10-20 23:11 ` Sean Christopherson [this message]
2021-10-21 2:24 ` Amy Parker
2021-10-21 14:31 ` Paolo Bonzini
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=YXCiM2iKZuiwnfjj@google.com \
--to=seanjc@google.com \
--cc=apark0006@student.cerritos.edu \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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