summaryrefslogtreecommitdiffstats
path: root/usr.bin/top
diff options
context:
space:
mode:
authornwhitehorn <nwhitehorn@FreeBSD.org>2011-05-31 15:11:43 +0000
committernwhitehorn <nwhitehorn@FreeBSD.org>2011-05-31 15:11:43 +0000
commita69e106b2fac0817484b6b395a4bfcabef513310 (patch)
tree02ea093d9809e917fd683ac9ee2c87d27aa454e6 /usr.bin/top
parent3e43795a7a21a21ba53f04ea258e3e79a7a34e9d (diff)
downloadFreeBSD-src-a69e106b2fac0817484b6b395a4bfcabef513310.zip
FreeBSD-src-a69e106b2fac0817484b6b395a4bfcabef513310.tar.gz
On multi-core, multi-threaded PPC systems, it is important that the threads
be brought up in the order they are enumerated in the device tree (in particular, that thread 0 on each core be brought up first). The SLIST through which we loop to start the CPUs has all of its entries added with SLIST_INSERT_HEAD(), which means it is in reverse order of enumeration and so AP startup would always fail in such situations (causing a machine check or RTAS failure). Fix this by changing the SLIST into an STAILQ, and inserting new CPUs at the end. Reviewed by: jhb
Diffstat (limited to 'usr.bin/top')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud