Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Aniket Sahu <asahu1x@linux.ibm.com>
To: Chinmay Rath <rathc@linux.ibm.com>, thuth@redhat.com
Cc: npiggin@gmail.com, harshpb@linux.ibm.com, lvivier@redhat.com,
	linuxppc-dev@lists.ozlabs.org, kvm@vger.kernel.org,
	andrew.jones@linux.dev, sbhat@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v2 0/6] powerpc improvements
Date: Tue, 21 Jul 2026 22:36:35 +0530	[thread overview]
Message-ID: <7cf674d9-6928-47a3-9d80-c1bd22ae6f7b@linux.ibm.com> (raw)
In-Reply-To: <20260719130027.2347519-1-rathc@linux.ibm.com>

On Sun, 19 Jul 2026, Chinmay Rath wrote: > This series aims to add a 
couple of new powerpc tests and improve > the powerpc build structure. 
Tested on POWER10 (native KVM, ppc64le). Tested-by: Aniket Sahu 
<asahu1x@linux.ibm.com> --- Environment --- Host CPU : POWER10 
(architected), altivec supported Kernel : Linux 7.0.0-27-generic 
#27-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun 18 19:14:19 UTC 2026 ppc64le 
GNU/Linux OS : Ubuntu 26.04 LTS (Resolute Raccoon) QEMU : 10.2.1 (Debian 
1:10.2.1+ds-1ubuntu3.1) Accelerator: KVM (-accel kvm -machine 
pseries,cap-ccf-assist=off) Branch : origin/ppc64 @ dde8f397 --- Test: 
pmu (Patch 1) --- $ ./run_tests.sh -a powerpc pmu PASS pmu (22 tests, 1 
known failure) Full log: timeout -k 1s --foreground 90s \ 
/usr/bin/qemu-system-ppc64 -nodefaults -accel kvm \ -machine 
pseries,cap-ccf-assist=off -bios powerpc/boot_rom.bin \ -display none 
-serial stdio -kernel powerpc/pmu.elf -smp 1 PASS: pmu: pmc56: PMC5 
zeroed PASS: pmu: pmc56: PMC6 zeroed PASS: pmu: pmc56: PMC5 frozen PASS: 
pmu: pmc56: PMC6 frozen PASS: pmu: pmc56: PMC5 counting PASS: pmu: 
pmc56: PMC6 counting PASS: pmu: pmc56: PMC6 ratio to reported clock 
frequency is 116% PASS: pmu: pmc56: PMC5 counts instructions precisely 
900 PASS: pmu: pmc56: PMC5 counts instructions exactly 21 PASS: pmu: 
pmc56: PMC5 counts instructions with branch 21 PASS: pmu: pmc56: PMC5 
counts instructions wth conditional branch 24 PASS: pmu: pmc56: PMC5 
counts instructions with illegal instruction PASS: pmu: pmc56: PMC5 
counts instructions with fault PASS: pmu: pmc56: PMC5 counts 
instructions with syscall PASS: pmu: pmc56: PMC5 counts instructions 
with rfid 2 PASS: pmu: pmc56: PMC5 counts instructions with ldat PASS: 
pmu: pmi: PMAO caused interrupt PASS: pmu: bhrb: BHRB is frozen PASS: 
pmu: bhrb: BHRB has been written KFAIL: pmu: bhrb: BHRB has written 8 
entries PASS: pmu: bhrb: BHRB has written 4 entries PASS: pmu: bhrb: 
correct conditional branch address SUMMARY: 22 tests, 1 known failure 
EXIT: STATUS=1 Note: The KFAIL on "BHRB has written 8 entries" is 
expected. POWER10 records 4 BHRB entries when other threads are active 
on the core; the test explicitly accounts for this with a fallback 
4-entry check which passes. STATUS=1 is the correct exit code when known 
failures exist. --- Test: selftest-setup (Patch 3/build structure) --- $ 
./run_tests.sh -a powerpc selftest-setup PASS selftest-setup (2 tests) 
Full log: timeout -k 1s --foreground 90s \ /usr/bin/qemu-system-ppc64 
-nodefaults -accel kvm \ -machine pseries,cap-ccf-assist=off -bios 
powerpc/boot_rom.bin \ -display none -serial stdio -kernel 
powerpc/selftest.elf \ -smp 2 -append setup smp=2 mem=1024 -m 1g PASS: 
selftest: setup: smp: nr_cpus_present = 2 PASS: selftest: setup: mem: 
size = 1024 MB SUMMARY: 2 tests EXIT: STATUS=1 --- Test: selftest-panic 
(Patches 5 & 6) --- $ ./run_tests.sh -a powerpc selftest-panic PASS 
selftest-panic Full log: run_panic timeout -k 1s --foreground 90s \ 
/usr/bin/qemu-system-ppc64 -nodefaults -accel kvm \ -machine 
pseries,cap-ccf-assist=off -bios powerpc/boot_rom.bin \ -display none 
-serial stdio -kernel powerpc/selftest.elf \ -smp 1 -append panic 
qemu-system-ppc64: OS terminated: rtas_os_panic PASS: guest panicked 
EXIT: STATUS=1 Note: The panic test validates both the new 
rtas_os_panic() RTAS call (Patch 6) and the run_panic() exit status fix 
(Patch 5). QEMU exits with "OS terminated: rtas_os_panic" confirming the 
ibm,os-term RTAS token is correctly invoked, and the test runner 
correctly identifies this as a successful (expected) panic. Aniket Sahu

  parent reply	other threads:[~2026-07-21 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-19 13:00 [kvm-unit-tests PATCH v2 0/6] powerpc improvements Chinmay Rath
2026-07-19 13:00 ` [kvm-unit-tests PATCH v2 1/6] powerpc: add pmu tests Chinmay Rath
2026-07-19 13:00 ` [kvm-unit-tests PATCH v2 2/6] configure: Make arch_libdir a first-class entity Chinmay Rath
2026-07-19 13:00 ` [kvm-unit-tests PATCH v2 3/6] powerpc: Remove remnants of ppc64 directory and build structure Chinmay Rath
2026-07-19 13:00 ` [kvm-unit-tests PATCH v2 4/6] powerpc: gitlab CI update Chinmay Rath
2026-07-19 13:00 ` [kvm-unit-tests PATCH v2 5/6] scripts/arch-run.bash: Fix run_panic() success exit status Chinmay Rath
2026-07-19 13:00 ` [kvm-unit-tests PATCH v2 6/6] powerpc: Add a panic test Chinmay Rath
2026-07-20  9:30 ` [kvm-unit-tests PATCH v2 0/6] powerpc improvements Thomas Huth
2026-07-20 12:17   ` Chinmay Rath
2026-07-21 17:06 ` Aniket Sahu [this message]
2026-07-21 17:12   ` Aniket Sahu

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=7cf674d9-6928-47a3-9d80-c1bd22ae6f7b@linux.ibm.com \
    --to=asahu1x@linux.ibm.com \
    --cc=andrew.jones@linux.dev \
    --cc=harshpb@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lvivier@redhat.com \
    --cc=npiggin@gmail.com \
    --cc=rathc@linux.ibm.com \
    --cc=sbhat@linux.ibm.com \
    --cc=thuth@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