Date: Mon, 09 Nov 2015 02:23:15 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204376] Cavium ThunderX system heavily loaded while at db> prompt Message-ID: <bug-204376-8-cSABijm8UW@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-204376-8@https.bugs.freebsd.org/bugzilla/> References: <bug-204376-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204376 --- Comment #2 from Conrad E. Meyer <cem@freebsd.org> --- If ARM is anything like amd64, it just spinwaits in IPI_STOP (waiting for the CPU to be re-enabled). On amd64 you could reduce it to 2 CPUs spinning pretty easily (hlt any non-panic and non-BSP core -- they'll never be needed until reboot). But that still leaves 2 CPUs spinning. The patch attempted to hlt all non-panic CPUs in IPI_STOP, but leave interrupts enabled so they could be woken again. This does Not Work Well in panic context (I forget the details, but if you've paniced you really don't want normal interrupt code running on the non-ddb CPU(s)). -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204376-8-cSABijm8UW>