qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH RFC V2 4/4] Add virtv2 machine that uses GIC-500


From: Pavel Fedin
Subject: Re: [Qemu-devel] [PATCH RFC V2 4/4] Add virtv2 machine that uses GIC-500
Date: Thu, 07 May 2015 16:12:26 +0300

 Hello!

>  My current guest kernel is v3.19.5. I will test on 4.1rc2 soon.

 Retested with 4.1.0rc2 (linux-stable.git master). Works perfectly fine with up 
to 8 CPUs. Here is boot log from 16 CPUs, listing potential problems:
--- cut ---
Initializing cgroup subsys memory
Initializing cgroup subsys hugetlb
hw perfevents: no hardware support available
EFI services will not be available.
CPU1: Booted secondary processor
Detected PIPT I-cache on CPU1
CPU1: found redistributor 1 region 0:0x0000000008060000
CPU2: Booted secondary processor
Detected PIPT I-cache on CPU2
CPU2: found redistributor 2 region 0:0x0000000008080000
CPU3: Booted secondary processor
Detected PIPT I-cache on CPU3
CPU3: found redistributor 3 region 0:0x00000000080a0000
CPU4: Booted secondary processor
Detected PIPT I-cache on CPU4
CPU4: found redistributor 4 region 0:0x00000000080c0000
CPU5: Booted secondary processor
Detected PIPT I-cache on CPU5
CPU5: found redistributor 5 region 0:0x00000000080e0000
CPU6: Booted secondary processor
Detected PIPT I-cache on CPU6
CPU6: found redistributor 6 region 0:0x0000000008100000
CPU7: Booted secondary processor
Detected PIPT I-cache on CPU7
CPU7: found redistributor 7 region 0:0x0000000008120000
psci: failed to boot CPU8 (-22)
CPU8: failed to boot: -22
psci: failed to boot CPU9 (-22)
CPU9: failed to boot: -22
psci: failed to boot CPU10 (-22)
CPU10: failed to boot: -22
psci: failed to boot CPU11 (-22)
CPU11: failed to boot: -22
psci: failed to boot CPU12 (-22)
CPU12: failed to boot: -22
psci: failed to boot CPU13 (-22)
CPU13: failed to boot: -22
psci: failed to boot CPU14 (-22)
CPU14: failed to boot: -22
psci: failed to boot CPU15 (-22)
CPU15: failed to boot: -22
Brought up 8 CPUs
SMP: Total of 8 processors activated.
CPU: All CPU(s) started at EL1
alternatives: patching kernel code
devtmpfs: initialized
DMI not present or invalid.
clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 
19112604462750000 ns
NET: Registered protocol family 16
cpuidle: using governor ladder
cpuidle: using governor menu
vdso: 2 pages (1 code @ ffffffc000819000, 1 data @ ffffffc000818000)
hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
DMA: preallocated 256 KiB pool for atomic allocations
Serial: AMBA PL011 UART driver
genirq: Setting trigger mode 1 for irq 9 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 10 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 11 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 12 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 13 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 14 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 15 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 16 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 17 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 18 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 19 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 20 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 25 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 26 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 27 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 28 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 29 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 30 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 31 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 32 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 33 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 34 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 35 failed (gic_set_type+0x0/0x78)
genirq: Setting trigger mode 1 for irq 36 failed (gic_set_type+0x0/0x78)
9000000.pl011: ttyAMA0 at MMIO 0x9000000 (irq = 38, base_baud = 0) is a PL011 
rev1
console [ttyAMA0] enabled
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switched to clocksource arch_sys_counter
NET: Registered protocol family 2
--- сut ---

 So far, i think the GICv3 functionality is OK. Here is my line.

Tested-by: Pavel Fedin <address@hidden>

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia





reply via email to

[Prev in Thread] Current Thread [Next in Thread]