Date: Sat, 28 Aug 2010 01:46:16 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Jung-uk Kim <jkim@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org Subject: Re: 8.1-PRERELEASE: CPU packages not detected correctly Message-ID: <4C784038.4070305@icyb.net.ua> In-Reply-To: <201008271833.42133.jkim@FreeBSD.org> References: <201007141414.o6EEEUx9014690@lurza.secnetix.de> <201008271743.29393.jkim@FreeBSD.org> <4C7835E6.6070309@icyb.net.ua> <201008271833.42133.jkim@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/08/2010 01:33 Jung-uk Kim said the following: > If you are really up to this, it has to be a two-pass process. Even > then, the dmesg won't be pretty because the topology can only be > "announced" after all APs have been started. I mean, nobody's going > to like to see a message like this from dmesg output: > > ... > ACPI APIC Table: <FOOBAR> > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > > --- >8 --- Snip several hundred lines! --- >8 --- > > SMP: AP CPU #1 Launched! > FreeBSD/SMP: 1 package(s) x 2 core(s) > Root mount waiting for: usbus5 usbus2 > Root mount waiting for: usbus5 usbus2 > ... > > In fact, I implemented something like that while I was writing the > patch but I discarded it for an obvious reason. ;-) Well, I was just going to write that I would still keep the assumption that physical packages are identical :-) Not nice, but messing with APs I don't want :) > Also, don't forget jhb's work based on ACPI affinity tables. Not sure how they are applicable here. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C784038.4070305>