qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [Qemu-ppc] [PATCH RFC] spapr: ignore interrupts during


From: Nikunj A Dadhania
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH RFC] spapr: ignore interrupts during reset state
Date: Thu, 13 Jul 2017 13:25:59 +0530

Cédric Le Goater <address@hidden> writes:

>>> How about the following, we do not report work until MSR_EE is disabled:
>> 
>> With this fix, I could test the XIVE<->XICS transitions at reboot 
>> under TCG. However, the second boot is very slow for some reason. 
>
> hmm, I am not sure this is related but I just got : 

Havent seen in my setup after around 10 reboot cycles, I was using 2
cores pseries setup. Lets give it some more testing. When did this
happen, during boot ?

>
> [   28.311559] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 23s! 
> [migration/0:10]
> [   28.311856] Modules linked in:
> [   28.312058] CPU: 0 PID: 10 Comm: migration/0 Not tainted 4.12.0+ #10
> [   28.312165] task: c00000007a842c00 task.stack: c00000007a12c000
> [   28.312214] NIP: c0000000001bf6b0 LR: c0000000001bf788 CTR: 
> c0000000001bf5b0
> [   28.312253] REGS: c00000007a12f9d0 TRAP: 0901   Not tainted  (4.12.0+)
> [   28.312284] MSR: 8000000002009033 <SF,VEC,EE,ME,IR,DR,RI,LE>

EE is enabled, so chances of interrupts getting ignored isnt there. More
over the code will trigger only when cs->halted is true.

> [   28.312399]   CR: 20004202  XER: 20040000
> [   28.312457] CFAR: c0000000001bf6c4 SOFTE: 1 
> [   28.312457] GPR00: c0000000001bf9c8 c00000007a12fc50 c00000000147f000 
> 0000000000000000 
> [   28.312457] GPR04: 0000000000000000 0000000000000000 0000000000000000 
> 0000000000000000 
> [   28.312457] GPR08: 0000000000000000 0000000000000001 0000000000000001 
> 000000000000002b 
> [   28.312457] GPR12: 0000000000000000 c00000000fdc0000 
> [   28.313029] NIP [c0000000001bf6b0] multi_cpu_stop+0x100/0x1f0
> [   28.313074] LR [c0000000001bf788] multi_cpu_stop+0x1d8/0x1f0
> [   28.313136] Call Trace:
> [   28.313334] [c00000007a12fc50] [c00000007a12fd30] 0xc00000007a12fd30 
> (unreliable)
> [   28.313428] [c00000007a12fca0] [c0000000001bf9c8] 
> cpu_stopper_thread+0xd8/0x220
> [   28.313480] [c00000007a12fd60] [c000000000113c10] 
> smpboot_thread_fn+0x290/0x2a0
> [   28.313571] [c00000007a12fdc0] [c00000000010dc04] kthread+0x164/0x1b0
> [   28.313640] [c00000007a12fe30] [c00000000000b268] 
> ret_from_kernel_thread+0x5c/0x74
> [   28.313742] Instruction dump:
> [   28.313924] 2fa90000 409e001c 813d0020 815d0010 39290001 915e0000 7c2004ac 
> 913d0020 
> [   28.314001] 2b9f0004 419e003c 7fe9fb78 7c210b78 <7c421378> 83fd0020 
> 7f89f840 409eff94 
>
> with 4 cores under mttcg.

Regards
Nikunj




reply via email to

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