mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
	linuxppc-dev@lists.ozlabs.org,
	Michael Ellerman <mpe@ellerman.id.au>,
	Christophe Leroy <chleroy@kernel.org>,
	Anushree Mathur <anushree.mathur@linux.ibm.com>,
	Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
	Harsh Prateek Bora <harshpb@linux.ibm.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Shrikanth Hegde <sshegde@linux.ibm.com>,
	linux-kernel@vger.kernel.org, Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH v5 1/9] KVM: PPC: selftests: add support for powerpc
Date: Sat, 03 Oct 2026 10:07:11 +0530	[thread overview]
Message-ID: <ld8fjt6w.ritesh.list@gmail.com> (raw)
In-Reply-To: <asAsTMn8naXCxhno@google.com>

Sean Christopherson <seanjc@google.com> writes:

> On Tue, Sep 22, 2026, Ritesh Harjani (IBM) wrote:
>> ---
>>  MAINTAINERS                                   |   2 +
>>  tools/testing/selftests/kvm/Makefile          |   2 +-
>>  tools/testing/selftests/kvm/Makefile.kvm      |  10 +
>>  .../testing/selftests/kvm/include/kvm_util.h  |   9 +
>>  .../selftests/kvm/include/powerpc/hcall.h     |  17 +
>>  .../kvm/include/powerpc/kvm_util_arch.h       |  22 +
>>  .../selftests/kvm/include/powerpc/ppc_asm.h   |  32 ++
>>  .../selftests/kvm/include/powerpc/processor.h |  39 ++
>>  .../selftests/kvm/include/powerpc/ucall.h     |  21 +
>>  tools/testing/selftests/kvm/lib/guest_modes.c |  20 +-
>>  tools/testing/selftests/kvm/lib/kvm_util.c    |   8 +
>>  .../selftests/kvm/lib/powerpc/handlers.S      |  93 ++++
>>  .../testing/selftests/kvm/lib/powerpc/hcall.c |  45 ++
>>  .../selftests/kvm/lib/powerpc/processor.c     | 512 ++++++++++++++++++
>>  .../testing/selftests/kvm/lib/powerpc/ucall.c |  22 +
>>  15 files changed, 851 insertions(+), 3 deletions(-)
>>  create mode 100644 tools/testing/selftests/kvm/include/powerpc/hcall.h
>>  create mode 100644 tools/testing/selftests/kvm/include/powerpc/kvm_util_arch.h
>>  create mode 100644 tools/testing/selftests/kvm/include/powerpc/ppc_asm.h
>>  create mode 100644 tools/testing/selftests/kvm/include/powerpc/processor.h
>>  create mode 100644 tools/testing/selftests/kvm/include/powerpc/ucall.h
>>  create mode 100644 tools/testing/selftests/kvm/lib/powerpc/handlers.S
>>  create mode 100644 tools/testing/selftests/kvm/lib/powerpc/hcall.c
>>  create mode 100644 tools/testing/selftests/kvm/lib/powerpc/processor.c
>>  create mode 100644 tools/testing/selftests/kvm/lib/powerpc/ucall.c
>> 
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index fc320b373656..35df0c39e991 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -14349,6 +14349,8 @@ F:	arch/powerpc/include/asm/kvm*
>>  F:	arch/powerpc/include/uapi/asm/kvm*
>>  F:	arch/powerpc/kernel/kvm*
>>  F:	arch/powerpc/kvm/
>> +F:	tools/testing/selftests/kvm/*/powerpc/
>> +F:	tools/testing/selftests/kvm/powerpc/
>
> I don't think sending KVM PPC selftests changes through the PPC tree will work.
> It's "fine" for KVM PPC changes because the volume of KVM PPC changes is low and
> rarely modifies anything outside of arch/powerpc.
>
> KVM selftests tend to have a lot more cross-arch and/or common code modifications,
> i.e. I think we'll be setting ourselves up for pain if we don't route all KVM
> selftests changes through Paolo's tree.
>

Sure, since enabling kvm selftests on powerpc has quite a few common
changes in cross-arch, so it make sense to take it via common tree which
it already uses.

BTW - the above file name paths are just so that we can have people cc
linuxppc-dev too, for powerpc kvm selftests changes.

> Does it maybe make sense to have all of KVM PPC route through Paolo?  Punting to
> PPC made sense when KVM PPC was on life support, but it looks like resuscitation
> was successful for at least some flavors of KVM PPC?

Today, I think it is getting managed, as long as the core/UAPI changes
are routed via Paolo and/or via ACK from both maintainers.

However, for PPC kvm selftests - let's do as discussed - to take it via
common kvm tree.


Thanks again Sean, for the review. I will soon post v6 with the
suggested approach.

-ritesh

  reply	other threads:[~2026-10-05  3:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-22 18:28 [PATCH v5 0/9] KVM: selftests: add powerpc support Ritesh Harjani (IBM)
2026-09-22 18:28 ` [PATCH v5 1/9] KVM: PPC: selftests: add support for powerpc Ritesh Harjani (IBM)
2026-10-02 22:12   ` Sean Christopherson
2026-10-03  4:37     ` Ritesh Harjani [this message]
2026-09-22 18:28 ` [PATCH v5 2/9] KVM: selftests: Enable kvm_create_max_vcpus test " Ritesh Harjani (IBM)
2026-09-22 18:28 ` [PATCH v5 3/9] KVM: selftests: Don't limit LE dirty-bitmap bitops to s390x Ritesh Harjani (IBM)
2026-09-22 18:28 ` [PATCH v5 4/9] KVM: selftests: Split out a KVM_CREATE_VCPU helper that can fail Ritesh Harjani (IBM)
2026-09-22 18:28 ` [PATCH v5 5/9] KVM: selftests: Make kvm_create_max_vcpus tolerate ENOMEM Ritesh Harjani (IBM)
2026-10-02 22:16   ` Sean Christopherson
2026-10-03  5:45     ` Ritesh Harjani
2026-09-22 18:28 ` [PATCH v5 6/9] KVM: selftests: Limit the number of VM creates in hardware_disable_test Ritesh Harjani (IBM)
2026-10-02 22:19   ` Sean Christopherson
2026-10-03  6:01     ` Ritesh Harjani
2026-09-22 18:28 ` [PATCH v5 7/9] KVM: PPC: selftests: Make nested case on pseries LPARs as resource constrained Ritesh Harjani (IBM)
2026-09-22 18:28 ` [PATCH v5 8/9] KVM: PPC: selftests: Skip idle-page check when running nested on pseries LPAR Ritesh Harjani (IBM)
2026-09-22 18:28 ` [PATCH v5 9/9] KVM: selftests: Move memslot_perf_test off the 256M ELF load address Ritesh Harjani (IBM)
2026-10-02 22:28   ` Sean Christopherson
2026-09-29  1:35 ` [PATCH v5 0/9] KVM: selftests: add powerpc support Ritesh Harjani
2026-10-02 22:38   ` Sean Christopherson
2026-10-03  6:46     ` Ritesh Harjani
2026-10-05  2:39       ` Sean Christopherson
2026-10-05  4:25         ` Ritesh Harjani
2026-10-05  6:08           ` Sean Christopherson
2026-09-29  5:49 ` Anushree Mathur

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=ld8fjt6w.ritesh.list@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=anushree.mathur@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=harshpb@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    --cc=sshegde@linux.ibm.com \
    --cc=venkat88@linux.ibm.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®