Date: Fri, 15 Feb 2019 15:17:10 -0600 From: Justin Hibbits <chmeeedalf@gmail.com> To: Mark Millard via freebsd-ppc <freebsd-ppc@freebsd.org> Subject: Re: Some evidence about the PowerMac G5 multiprocessor boot hang ups with the modern VM_MAX_KERNEL_ADDRESS value Message-ID: <20190215151710.35545a26@ralga.knownspace> In-Reply-To: <1F3411CF-3D28-43C0-BEF1-4672B5CC1543@yahoo.com> References: <11680D15-D43D-4115-AF4F-5F6E4E0022C9@yahoo.com> <9FBCA729-CE80-44CD-8873-431853E55231@yahoo.com> <1F3411CF-3D28-43C0-BEF1-4672B5CC1543@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 15 Feb 2019 11:51:26 -0800 Mark Millard via freebsd-ppc <freebsd-ppc@freebsd.org> wrote: > Old: 0xe0000000013ff0?? > New: 0xe000000087fd20?? The addresses are pretty inconsequential, since they're virtual addresses. It would be nice to be able to profile how far a CPU gets in its launch (writing a value to a well-known address, 0xc000000000000010, or such, anywhere in the bottom 256 bytes of space really). If you add writes to that address, we can track the progress at panic time. I'd presume all APs would behave the same way, so no need for lock management, or isolation between them. - Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190215151710.35545a26>