Built and tested qemu-ppc64le on ppc64le host

Test environment:
- Host: ppc64le Linux (POWER10)
- QEMU version: v11.0.50 (v11.0.0-1849-g193963218a-dirty) - upstream qemu with 
patch applied
- Target: ppc64le-linux-user

Manual tests performed:
- Verified /proc/cpuinfo is readable by PPC binaries under qemu-user
- Verified qemu-ppc64le -cpu POWER10 /bin/cat /proc/cpuinfo returns the 
expected PPC-specific cpuinfo output
- Tested POWER8, POWER9, and POWER10 CPU models
- Confirmed different PVR values for different CPU types
- Verified all required fields present (processor, cpu, clock, revision, 
timebase, platform, model, machine)
- CPU count correctly reported (48 online CPUs)
- Tested with both custom test program and system binaries (/bin/cat)

Test Logs:
1. POWER9 CPU model test:
$ qemu-ppc64le -cpu POWER9 /tmp/test-cpuinfo | head -10
=== /proc/cpuinfo via qemu-user ===
processor:      : 0
cpu:            : POWER9, altivec supported
clock           : 3425.000000MHz
revision        : 2.2 (pvr 004e 1202)

processor:      : 1
cpu:            : POWER9, altivec supported
clock           : 3425.000000MHz
revision        : 2.2 (pvr 004e 1202)

2. POWER10 CPU model test:
$ qemu-ppc64le -cpu POWER10 /tmp/test-cpuinfo | head -10
=== /proc/cpuinfo via qemu-user ===
processor:      : 0
cpu:            : POWER10, altivec supported
clock           : 3425.000000MHz
revision        : 2.0 (pvr 0080 0200)

processor:      : 1
cpu:            : POWER10, altivec supported
clock           : 3425.000000MHz
revision        : 2.0 (pvr 0080 0200)

3. System binary test:
$ qemu-ppc64le -cpu POWER9 /bin/cat /proc/cpuinfo | tail -5
timebase        : 512000000
platform        : pSeries
model           : IBM pSeries (QEMU user v11.0.50)
machine         : CHRP IBM pSeries

Qemu Unit tests:
make check: 118/118 tests PASSED
Ok:                118
Fail:              0

All tests passed. The patch correctly implements /proc/cpuinfo for PPC 
user-mode emulation without breaking existing functionality. Output format is 
consistent and provides accurate CPU information.

Tested-by: Misbah Anjum N <[email protected]>

Thanks,
Misbah Anjum N

Reply via email to