From: Thomas Huth <thuth@redhat.com>
To: Harsh Prateek Bora <harshpb@linux.ibm.com>,
Chinmay Rath <rathc@linux.ibm.com>
Cc: npiggin@gmail.com, lvivier@redhat.com,
linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
andrew.jones@linux.dev, sbhat@linux.ibm.com,
Misbah Anjum N <misanjum@linux.ibm.com>,
Anushree Mathur <anushree.mathur@linux.ibm.com>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: Re: [kvm-unit-tests PATCH 4/6] powerpc: gitlab CI update
Date: Thu, 9 Jul 2026 17:16:15 +0200 [thread overview]
Message-ID: <73573868-2fb9-445d-b5c6-02166a0feb25@redhat.com> (raw)
In-Reply-To: <8c9b739c-8a9b-4e9a-8e43-7b1a6e1aa330@linux.ibm.com>
On 09/07/2026 16.32, Harsh Prateek Bora wrote:
> + folks who might be interested.
>
> Hi Thomas,
>
> On 09/07/26 12:16 pm, Thomas Huth wrote:
>>> +++ b/powerpc/unittests.cfg
>>> @@ -24,6 +24,14 @@ file = selftest-migration.elf
>>> machine = pseries
>>> groups = selftest migration
>>> +# make a kvm-only version for CI for now
>>> +# TCG accel support with Qemu and distro release used in gitlab CI needs
>>> to checked.
>>> +[selftest-migration-ci]
>>> +file = selftest-migration.elf
>>> +machine = pseries
>>> +groups = nodefault selftest migration
>>> +accel = kvm
>>
>> This does not make sense (or I don't understand it) - gitlab-CI currently
>> only runs with TCG for the ppc64 jobs, so adding a separate test for this
>> with "accel = kvm" just adds a job there that will always be skipped. What
>> should this be good for?
>
> I understand it may get skipped in gitlab CI for kvm-unit-tests,
> but it might be helpful to those who can run it on their Power HW.
> If the job can safely skip on non-ppc HW, I hope it's fine?
> We would like to get it integrated in IBM's internal CI with Power HW.
You mean you also use a gitlab instance internally within IBM? ... otherwise
it does not make sense to add this to the .gitlab-ci.yml file (which you did
earlier in this patch).
Thomas
next prev parent reply other threads:[~2026-07-09 15:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 10:51 [kvm-unit-tests PATCH 0/6] powerpc improvements Chinmay Rath
2026-07-08 10:51 ` [kvm-unit-tests PATCH 1/6] powerpc: add pmu tests Chinmay Rath
2026-07-08 10:51 ` [kvm-unit-tests PATCH 2/6] configure: Make arch_libdir a first-class entity Chinmay Rath
2026-07-08 10:51 ` [kvm-unit-tests PATCH 3/6] powerpc: Remove remnants of ppc64 directory and build structure Chinmay Rath
2026-07-08 10:51 ` [kvm-unit-tests PATCH 4/6] powerpc: gitlab CI update Chinmay Rath
2026-07-09 6:46 ` Thomas Huth
2026-07-09 14:32 ` Harsh Prateek Bora
2026-07-09 15:16 ` Thomas Huth [this message]
2026-07-09 16:08 ` Harsh Prateek Bora
2026-07-09 16:33 ` Thomas Huth
2026-07-08 10:51 ` [kvm-unit-tests PATCH 5/6] scripts/arch-run.bash: Fix run_panic() success exit status Chinmay Rath
2026-07-08 10:51 ` [kvm-unit-tests PATCH 6/6] powerpc: Add a panic test Chinmay Rath
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=73573868-2fb9-445d-b5c6-02166a0feb25@redhat.com \
--to=thuth@redhat.com \
--cc=andrew.jones@linux.dev \
--cc=anushree.mathur@linux.ibm.com \
--cc=harshpb@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lvivier@redhat.com \
--cc=maddy@linux.ibm.com \
--cc=misanjum@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=rathc@linux.ibm.com \
--cc=sbhat@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