From: Sean Christopherson <seanjc@google.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: kvm@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Nicholas Piggin <npiggin@gmail.com>,
linux-kselftest@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 0/2] KVM: PPC: support kvm selftests
Date: Wed, 22 Mar 2023 10:41:08 -0700 [thread overview]
Message-ID: <ZBs9tGkI5OQqtIqs@google.com> (raw)
In-Reply-To: <87ilf0nc95.fsf@mpe.ellerman.id.au>
On Thu, Mar 16, 2023, Michael Ellerman wrote:
> Nicholas Piggin <npiggin@gmail.com> writes:
> > Hi,
> >
> > This series adds initial KVM selftests support for powerpc
> > (64-bit, BookS).
>
> Awesome.
>
> > It spans 3 maintainers but it does not really
> > affect arch/powerpc, and it is well contained in selftests
> > code, just touches some makefiles and a tiny bit headers so
> > conflicts should be unlikely and trivial.
> >
> > I guess Paolo is the best point to merge these, if no comments
> > or objections?
>
> Yeah. If it helps:
>
> Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
What is the long term plan for KVM PPC maintenance? I was under the impression
that KVM PPC was trending toward "bug fixes only", but the addition of selftests
support suggests otherwise.
I ask primarily because routing KVM PPC patches through the PPC tree is going to
be problematic if KVM PPC sees signficiant development. The current situation is
ok because the volume of patches is low and KVM PPC isn't trying to drive anything
substantial into common KVM code, but if that changes...
My other concern is that for selftests specifically, us KVM folks are taking on
more maintenance burden by supporting PPC. AFAIK, none of the people that focus
on KVM selftests in any meaningful capacity have access to PPC hardware, let alone
know enough about the architecture to make intelligent code changes.
Don't get me wrong, I'm very much in favor of more testing, I just don't want KVM
to get left holding the bag.
next prev parent reply other threads:[~2023-03-22 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 3:17 [PATCH 0/2] KVM: PPC: support kvm selftests Nicholas Piggin
2023-03-16 3:17 ` [PATCH 1/2] KVM: PPC: Add kvm selftests support for powerpc Nicholas Piggin
2023-03-29 20:19 ` Sean Christopherson
2023-04-02 0:48 ` Nicholas Piggin
2023-03-16 3:17 ` [PATCH 2/2] KVM: PPC: Add basic framework tests for kvm selftests Nicholas Piggin
2023-03-16 11:53 ` [PATCH 0/2] KVM: PPC: support " Michael Ellerman
2023-03-22 17:41 ` Sean Christopherson [this message]
2023-03-27 5:37 ` Nicholas Piggin
2023-03-27 17:43 ` Sean Christopherson
2023-03-28 6:49 ` Nicholas Piggin
2023-03-28 9:07 ` Michael Ellerman
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=ZBs9tGkI5OQqtIqs@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=shuah@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).