#
8a8daeaf |
|
23-Apr-2024 |
Lexi Winter <lexi@le-Fay.ORG> |
sys/*/conf: do not use "../../conf/" when including std.* Since config(8) searches sys/conf by default, there's no need to specify the full relative path here; replace it by the filename alone. Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1124
|
#
031beb4e |
|
16-Aug-2023 |
Warner Losh <imp@FreeBSD.org> |
sys: Remove $FreeBSD$: one-line sh pattern Remove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
|
#
c1a14887 |
|
20-May-2021 |
Ceri Davies <ceri@FreeBSD.org> |
sys/*/conf/*, docs: fix links to handbook While here, fix all links to older en_US.ISO8859-1 documentation in the src/ tree. PR: 255026 Reported by: Michael Büker <freebsd@michael-bueker.de> Reviewed by: dbaio Approved by: blackend (mentor), re (gjb) MFC after: 10 days Differential Revision: https://reviews.freebsd.org/D30265
|
#
6eebda3b |
|
14-Jan-2021 |
Andrew Turner <andrew@FreeBSD.org> |
Split out the NODEBUG options to a common file This is the superset of the nooptions found in the -DEBUG kernels. Reviewed by: emaste, manu Sponsored by: Innovate UK Differential Revision: https://reviews.freebsd.org/D28152
|
#
37bd4ba9 |
|
12-Apr-2020 |
Conrad Meyer <cem@FreeBSD.org> |
Add queue(2) debug macros as build options Add QUEUE_MACRO_DEBUG_TRACE and QUEUE_MACRO_DEBUG_TRASH as proper kernel options. While here, alpha-sort the debug section of sys/conf/options. Enable QUEUE_MACRO_DEBUG_TRASH in amd64 GENERIC (but not GENERIC-NODEBUG) kernels. It is similar in nature and cost to other use-after-free pointer trashing we do in GENERIC. It is probably reasonable to enable in any arch GENERIC kernel that defines INVARIANTS.
|
#
dfa4261d |
|
27-Feb-2020 |
Brooks Davis <brooks@FreeBSD.org> |
Remove trailing whitespace.
|
#
85e06c72 |
|
18-Nov-2019 |
Mark Johnston <markj@FreeBSD.org> |
Set MALLOC_DEBUG_MAXZONES=1 in GENERIC-NODEBUG configurations. The purpose of this option is to make it easier to track down memory corruption bugs by reducing the number of malloc(9) types that might have recently been associated with a given chunk of memory. However, it increases fragmentation and is disabled in release kernels. MFC after: 2 weeks Sponsored by: The FreeBSD Foundation
|
#
524553f5 |
|
29-Jan-2019 |
Andrew Turner <andrew@FreeBSD.org> |
Extract the coverage sanitizer KPI to a new file. This will allow multiple consumers of the coverage data to be compiled into the kernel together. The only requirement is only one can be registered at a given point in time, however it is expected they will only register when the coverage data is needed. A new kernel conflig option COVERAGE is added. This will allow kcov to become a module that can be loaded as needed, or compiled into the kernel. While here clean up the #include style a little. Reviewed by: kib Sponsored by: DARPA, AFRL Differential Revision: https://reviews.freebsd.org/D18955
|
#
14d13423 |
|
23-May-2018 |
Matt Macy <mmacy@FreeBSD.org> |
take NUMA out
|
#
e98bbcf9 |
|
23-May-2018 |
Matt Macy <mmacy@FreeBSD.org> |
libpmcstat: compile in events based on json description
|
#
a2aef24a |
|
29-Oct-2017 |
Eitan Adler <eadler@FreeBSD.org> |
Update several more URLs - Primarily http -> https - Primarily FreeBSD project URLs
|
#
8532d381 |
|
31-Oct-2016 |
Conrad Meyer <cem@FreeBSD.org> |
Add BUF_TRACKING and FULL_BUF_TRACKING buffer debugging Upstream the BUF_TRACKING and FULL_BUF_TRACKING buffer debugging code. This can be handy in tracking down what code touched hung bios and bufs last. The full history is especially useful, but adds enough bloat that it shouldn't be enabled in release builds. Function names (or arbitrary string constants) are tracked in a fixed-size ring in bufs. Bios gain a pointer to the upper buf for tracking. SCSI CCBs gain a pointer to the upper bio for tracking. Reviewed by: markj Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D8366
|
#
bd19924f |
|
02-Dec-2014 |
George V. Neville-Neil <gnn@FreeBSD.org> |
This configuration file removes several debugging options, including WITNESS and INVARIANTS checking, which are known to have significant performance impact on running systems. When benchmarking new features this kernel should be used instead of the standard GENERIC. This kernel configuration should never appear outside of the HEAD of the FreeBSD tree.
|