diff options
author | jhb <jhb@FreeBSD.org> | 2015-04-15 16:52:34 +0000 |
---|---|---|
committer | jhb <jhb@FreeBSD.org> | 2015-04-15 16:52:34 +0000 |
commit | 5967aacd0bce7647e5b12fbabef30c75b0decd79 (patch) | |
tree | a167dd4c1d22cb5924d6e131bbee411eb4fae9f5 /sys/dev/mps/mpi/mpi2_init.h | |
parent | dcb9c46825addcba6c75a61e50bc71107b17f28d (diff) | |
download | FreeBSD-src-5967aacd0bce7647e5b12fbabef30c75b0decd79.zip FreeBSD-src-5967aacd0bce7647e5b12fbabef30c75b0decd79.tar.gz |
MFC 278325,280866:
Revert the IPI startup sequence to match what is described in the
Intel Multiprocessor Specification v1.4. The Intel SDM claims that
278325:
Revert the IPI startup sequence to match what is described in the
Intel Multiprocessor Specification v1.4. The Intel SDM claims that
the INIT IPIs here are invalid, but other systems follow the MP
spec instead.
While here, fix the IPI wait routine to accept a timeout in microseconds
instead of a raw spin count, and don't spin forever during AP startup.
Instead, panic if a STARTUP IPI is not delivered after 20 us.
280866:
Wait 100 microseconds for a local APIC to dispatch each startup-related IPI
rather than 20. The MP 1.4 specification states in Appendix B.2:
"A period of 20 microseconds should be sufficient for IPI dispatch to
complete under normal operating conditions".
(Note that this appears to be separate from the 10 millisecond (INIT) and
200 microsecond (STARTUP) waits after the IPIs are dispatched.) The
Intel SDM is silent on this issue as far as I can tell.
At least some hardware requires 60 microseconds as noted in the PR, so
bump this to 100 to be on the safe side.
PR: 196542, 197756
Diffstat (limited to 'sys/dev/mps/mpi/mpi2_init.h')
0 files changed, 0 insertions, 0 deletions