FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=upstream%2F11.0.0 2016-05-31T11:32:09Z 2016-05-31T11:32:09Z Andrew Turner andrew@FreeBSD.org 2016-05-31T11:32:09Z urn:sha1:1cb290d2f2458109fa492d300e21f102a41b6874 Obtained from: ABT Systems Ltd Sponsored by: The FreeBSD Foundation 2016-05-27T17:58:10Z Ruslan Bukin br@FreeBSD.org 2016-05-27T17:58:10Z urn:sha1:bdca9b1d5210a21fb572e99337515fbeac1f4f47 Pointed out by: andrew Sponsored by: DARPA, AFRL Sponsored by: HEIF5 2016-05-27T12:02:12Z Andrew Turner andrew@FreeBSD.org 2016-05-27T12:02:12Z urn:sha1:12aac6b55b21cfafe8eb042e24b4443c61b29548 former return the current status for the latter to use. Without this we could enable interrupts when they shouldn't be. It's still not quite right as it should only update the bits we care about, bit should be good enough until the correct fix can be tested. PR: 204270 Obtained from: ABT Systems Ltd Sponsored by: The FreeBSD Foundation 2016-05-24T17:38:27Z Bjoern A. Zeeb bz@FreeBSD.org 2016-05-24T17:38:27Z urn:sha1:9c759b587fd534db889ab766ccfa2d6657c12d1c defining VM_MIN_KERNEL_ADDRESS. Sponsored by: DARPA/AFRL 2016-05-24T16:41:37Z Ruslan Bukin br@FreeBSD.org 2016-05-24T16:41:37Z urn:sha1:fed1ca4b719c56c930f2259d80663cd34be812bb Sponsored by: DARPA, AFRL Sponsored by: HEIF5 2016-05-24T13:57:23Z Andrew Turner andrew@FreeBSD.org 2016-05-24T13:57:23Z urn:sha1:0d0da7691102c99bf37fd1cd029ffbd41af7f1d9 Obtained from: ABT Systems Ltd Sponsored by: The FreeBSD Foundation 2016-05-14T18:22:52Z John Baldwin jhb@FreeBSD.org 2016-05-14T18:22:52Z urn:sha1:fdce57a04219d7a36c6646950fde6c8bcd97c044 Currently, Application Processors (non-boot CPUs) are started by MD code at SI_SUB_CPU, but they are kept waiting in a "pen" until SI_SUB_SMP at which point they are released to run kernel threads. SI_SUB_SMP is one of the last SYSINIT levels, so APs don't enter the scheduler and start running threads until fairly late in the boot. This change moves SI_SUB_SMP up to just before software interrupt threads are created allowing the APs to start executing kernel threads much sooner (before any devices are probed). This allows several initialization routines that need to perform initialization on all CPUs to now perform that initialization in one step rather than having to defer the AP initialization to a second SYSINIT run at SI_SUB_SMP. It also permits all CPUs to be available for handling interrupts before any devices are probed. This last feature fixes a problem on with interrupt vector exhaustion. Specifically, in the old model all device interrupts were routed onto the boot CPU during boot. Later after the APs were released at SI_SUB_SMP, interrupts were redistributed across all CPUs. However, several drivers for multiqueue hardware allocate N interrupts per CPU in the system. In a system with many CPUs, just a few drivers doing this could exhaust the available pool of interrupt vectors on the boot CPU as each driver was allocating N * mp_ncpu vectors on the boot CPU. Now, drivers will allocate interrupts on their desired CPUs during boot meaning that only N interrupts are allocated from the boot CPU instead of N * mp_ncpu. Some other bits of code can also be simplified as smp_started is now true much earlier and will now always be true for these bits of code. This removes the need to treat the single-CPU boot environment as a special case. As a transition aid, the new behavior is available under a new kernel option (EARLY_AP_STARTUP). This will allow the option to be turned off if need be during initial testing. I plan to enable this on x86 by default in a followup commit in the next few days and to have all platforms moved over before 11.0. Once the transition is complete, the option will be removed along with the !EARLY_AP_STARTUP code. These changes have only been tested on x86. Other platform maintainers are encouraged to port their architectures over as well. The main things to check for are any uses of smp_started in MD code that can be simplified and SI_SUB_SMP SYSINITs in MD code that can be removed in the EARLY_AP_STARTUP case (e.g. the interrupt shuffling). PR: kern/199321 Reviewed by: markj, gnn, kib Sponsored by: Netflix 2016-05-05T13:54:50Z Ruslan Bukin br@FreeBSD.org 2016-05-05T13:54:50Z urn:sha1:d7dc6bae0391a8c92918893057450ab57796943a Tested on MIPS64. Sponsored by: DARPA, AFRL Sponsored by: HEIF5 2016-04-29T15:45:22Z Andriy Gapon avg@FreeBSD.org 2016-04-29T15:45:22Z urn:sha1:27b6c49726d82971f36a8f90073bbc12e48da665 MFC after: 2 weeks 2016-04-25T18:09:36Z Mark Johnston markj@FreeBSD.org 2016-04-25T18:09:36Z urn:sha1:cd8bbc382d859fa3a9b701bddb7b10f8b0de87f2 When this flag is turned on, DOF and DIF validation errors are printed to the kernel message buffer. This is useful for debugging. Also remove the debug.dtrace.debug sysctl, which has no effect.