FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=stable%2F13 2023-08-23T17:43:25Z 2023-08-23T17:43:25Z Warner Losh imp@FreeBSD.org 2023-08-22T01:31:27Z urn:sha1:3bc80996974a61a4223eae4c1ccd47b6ee32a48a Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/ Similar commit in current: (cherry picked from commit 685dc743dc3b) 2023-07-25T15:13:49Z Warner Losh imp@FreeBSD.org 2023-05-10T15:40:58Z urn:sha1:caa41f641755c935b036e17440a3b49329c904ed The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause. Discussed with: pfg MFC After: 3 days Sponsored by: Netflix (cherry picked from commit 4d846d260e2b9a3d4d0a701462568268cbfe7a5b) 2020-09-01T21:20:45Z Mateusz Guzik mjg@FreeBSD.org 2020-09-01T21:20:45Z urn:sha1:c3aa3bf97c3740d5fae933e315f925b20530975c 2020-05-13T18:07:37Z Kyle Evans kevans@FreeBSD.org 2020-05-13T18:07:37Z urn:sha1:c79cee71363ddaeb3c5ab7d3ccb87a11e1860d95 __builtin_unreachable doesn't raise any compile-time warnings/errors on its own, so problems with its usage can't be easily detected. While it would be nice for this situation to change and compilers to at least add a warning for trivial cases where local state means the instruction can't be reached, this isn't the case at the moment and likely will not happen. This commit adds an __assert_unreachable, whose intent is incredibly clear: it asserts that this instruction is unreachable. On INVARIANTS builds, it's a panic(), and on non-INVARIANTS it expands to __unreachable(). Existing users of __unreachable() are converted to __assert_unreachable, to improve debuggability if this assumption is violated. Reviewed by: mjg Differential Revision: https://reviews.freebsd.org/D23793 2020-03-07T00:55:46Z Mark Johnston markj@FreeBSD.org 2020-03-07T00:55:46Z urn:sha1:3fba886874ff09c0404b9c417f3c75bb34c1060f The intent is to provide a header that can be included by other headers without introducing too much pollution. smr.h depends on various headers and will likely grow over time, but is less likely to be required by system headers. Rename SMR_TYPE_DECLARE() to SMR_POINTER(): - One might use SMR to protect more than just pointers; it could be used for resizeable arrays, for example, so TYPE seems too generic. - It is useful to be able to define anonymous SMR-protected pointer types and the _DECLARE suffix makes that look wrong. Reviewed by: jeff, mjg, rlibby Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D23988 2020-02-22T16:20:04Z Kyle Evans kevans@FreeBSD.org 2020-02-22T16:20:04Z urn:sha1:cef81f8f01493b181925da69c963a301ae45710e This provides the needed hint to GCC and offers an annotation for readers to observe that it's in-fact impossible to hit this point. We'll get hit with a a -Wswitch error if the enum applicable to the switch above were to get expanded without the new value(s) being handled. 2020-02-19T22:34:22Z Jeff Roberson jeff@FreeBSD.org 2020-02-19T22:34:22Z urn:sha1:4b3dac72b3cb46aefaa8160911365b6d169643c9 possible enum in a switch statement. I verified that this emits nothing as expected on clang. radix relies on constant propagation to eliminate any branching from these access routines. Reported by: lwhsu/tinderbox 2020-02-19T19:58:31Z Jeff Roberson jeff@FreeBSD.org 2020-02-19T19:58:31Z urn:sha1:1ddda2eb2400a56995c5b7baed5e07bfe8bd21d5 The tree is kept correct for readers with store barriers and careful ordering. The existing object lock serializes writers. Consumers will be introduced in later commits. Reviewed by: markj, kib Differential Revision: https://reviews.freebsd.org/D23446 2018-06-24T13:08:05Z Mateusz Guzik mjg@FreeBSD.org 2018-06-24T13:08:05Z urn:sha1:a3d799fbb5f10466686444513c090fc731387061 Allocation explicitely initialized the 3 leading fields. The rest is an array which is supposed to be NULL-ed prior to deallocation. Delegate zeroing to the infrequently called object initializator. This gets rid of one of the most common memset consumers. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D15989 2018-02-06T22:06:59Z Gleb Smirnoff glebius@FreeBSD.org 2018-02-06T22:06:59Z urn:sha1:ae941b1b4ede879a2668e6d3fa5e8d6525ca4c4e o Call uma_startup1() after initializing kmem, vmem and domains. o Include 8 eight VM startup pages into uma_startup_count() calculation. o Account for vmem_startup() and vm_map_startup() preallocating pages. o Account for extra two allocations done by kmem_init() and vmem_create(). o Hardcode the place of execution of vm_radix_reserve_kva(). Using SYSINIT allowed several other SYSINITs to sneak in before it, thus bumping requirement for amount of boot pages.