Up to [cvs.NetBSD.org] / src / distrib / sets / lists / debug
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
Pull up following revision(s) (requested by riastradh in ticket #939): distrib/sets/lists/debug/module.md.amd64: revision 1.18 sys/modules/Makefile: revision 1.292 lib/libc/gen/arc4random.c: revision 1.34 lib/libc/gen/arc4random.c: revision 1.35 lib/libc/gen/arc4random.c: revision 1.36 lib/libc/gen/arc4random.c: revision 1.37 sys/kern/kern_entropy.c: revision 1.70 lib/libc/gen/arc4random.c: revision 1.38 sys/kern/kern_entropy.c: revision 1.71 lib/libc/gen/getentropy.3: revision 1.8 distrib/sets/lists/modules/md.amd64: revision 1.103 share/man/man4/rnd.4: revision 1.42 share/man/man4/rnd.4: revision 1.44 lib/libc/include/arc4random.h: revision 1.1 distrib/sets/lists/man/mi: revision 1.1786 sys/arch/i386/conf/GENERIC: revision 1.1258 sys/modules/acpivmgenid/acpivmgenid.ioconf: revision 1.1 sys/arch/amd64/conf/ALL: revision 1.190 distrib/sets/lists/debug/mi: revision 1.446 sys/arch/i386/conf/ALL: revision 1.521 lib/libc/gen/Makefile.inc: revision 1.219 distrib/sets/lists/debug/module.md.i386: revision 1.12 sys/dev/acpi/acpi_vmgenid.c: revision 1.1 sys/dev/acpi/acpi_vmgenid.c: revision 1.2 lib/libc/include/reentrant.h: revision 1.22 sys/arch/evbarm/conf/GENERIC64: revision 1.219 share/man/man4/Makefile: revision 1.735 distrib/sets/lists/modules/md.i386: revision 1.100 distrib/sets/lists/tests/mi: revision 1.1334 lib/libc/gen/arc4random.3: revision 1.22 sys/dev/acpi/files.acpi: revision 1.133 lib/libc/gen/arc4random.3: revision 1.23 tests/lib/libc/gen/t_arc4random.c: revision 1.1 sys/sys/entropy.h: revision 1.6 sys/arch/amd64/conf/GENERIC: revision 1.614 sys/modules/acpivmgenid/Makefile: revision 1.1 share/man/man4/acpivmgenid.4: revision 1.1 lib/libc/gen/Makefile.inc: revision 1.220 tests/lib/libc/gen/Makefile: revision 1.56 share/man/man4/acpivmgenid.4: revision 1.2 share/man/man4/acpivmgenid.4: revision 1.3 (all via patch) Catch up with all the lint warnings since exit on warning was disabled. Disable 'missing header declaration' and 'nested extern' warnings for now. acpivmgenid(4): New driver for virtual machine generation ID. Added to amd64/ALL and i386/ALL kernel configurations, and made available as a loadable module acpivmgenid.kmod on x86, for now. TBD: Add to all ACPI-supporting GENERIC kernels. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork entropy(9): Factor out subroutines to reset and gather entropy. `Reset' means we keep the data in the pool, but assume it had zero entropy. `Gather' means we request samples from all on-demand sources and wait for the synchronous ones to complete. No functional change intended, other than to expose new symbols -- just preparation to expose these to acpivmgenid(4), so it can use these when the VM host notifies us that we, the guest, have been cloned. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork acpivmgenid(4): Reset and gather entropy on VM clone notification. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork arc4random(3): Reseed if system entropy epoch changes. This can happen, for example, if the system is a VM instance, and the VM is cloned. This incurs the cost of a system call on every arc4random call, which is unfortunate, but 1. we don't currently have a (machine-independent) mechanism for exposing a read-only page to userland shared by the kernel to enable a cheaper access path to the entropy epoch; and 2. the algorithm here -- a simple application of ChaCha -- is likely also a bottleneck and could be much cheaper by (a) using sys/crypto/chacha for machine-dependent vectorized ChaCha code, and (b) filling a buffer (somewhere between a cipher block and a page) in a batch at a time, instead of running ChaCha to generate only 32 bytes at a time. So although this might be a performance hit, the security benefit is worthwhile and we have a clear path to do better than reversing the performance hit later. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork acpivmgenid(4): Nix BUGS that have been squashed. Reference kern.entropy.epoch for the remaining bug (which is a performance issue, not a security issue). PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork entropy(9): Allow unprivileged reads of sysctl kern.entropy.epoch. Applications need this in order to know when to reseed. (We should also expose it through a page shared read-only with userland for cheaper access, but until we do, let's let applications get at it through sysctl.) PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork arc4random.c: Fix test program. This isn't wired up anywhere, but let's reduce the bitrot. It was helpful in reminding me that kern.entropy.epoch was, for reasons I can't remember, restricted to privileged access. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork amd64, evbarm, i386: Add acpivmgenid(4) to GENERIC. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork rnd(4): Document kern.entropy.epoch is unprivileged and elaborate. Cross-reference acpivmgenid(4). PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork arc4random(3): Note that arc4random respects kern.entropy.epoch. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork Add debug info for new acpivmgenid module arc4random(3): Add automatic tests. This verifies that: - arc4random zeroes its state and reseeds itself on fork - arc4random reseeds itself on entropy consolidation (e.g., VM clone) - arc4random falls back to global state if it can't allocate local state because address space limits cause mmap to fail NOTE: This adds a new libc symbol __arc4random_global, but it's in the reserved namespace and only used by t_arc4random, so no libc minor bump. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork getentropy(3): Note intent to reseed on VM clone, and caveats. Tidy markup and pacify some mandoc -Tlint complaints while here. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork Bump dates on man pages recently updated to mention VM clones. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork arc4random(3): Pacify some of lint's complaints. PR kern/58632: getentropy(2) and arc4random(3) do not reseed on VM fork arc4random: suppress another lint warning
Pull up following revision(s) (requested by riastradh in ticket #936): sys/dev/acpi/apei_einjvar.h: revision 1.1 sys/dev/acpi/apei_cper.h: revision 1.2 distrib/sets/lists/debug/module.md.i386: revision 1.9 sys/dev/acpi/apei_hest.c: revision 1.1 sys/modules/apei/Makefile: revision 1.1 sys/dev/acpi/apei_hest.c: revision 1.2 distrib/sets/lists/modules/md.amd64: revision 1.101 sys/dev/acpi/apei_hest.c: revision 1.3 distrib/sets/lists/modules/md.amd64: revision 1.102 sys/modules/apei/apei.ioconf: revision 1.1 sys/dev/acpi/apei_bert.c: revision 1.1 distrib/sets/lists/man/mi: revision 1.1785 sys/dev/acpi/apei_bertvar.h: revision 1.1 sys/dev/acpi/apei.c: revision 1.1 sys/dev/acpi/apei.c: revision 1.2 sys/dev/acpi/apei.c: revision 1.3 sys/modules/Makefile: revision 1.283 sys/modules/Makefile: revision 1.284 sys/dev/acpi/apei_reg.c: revision 1.1 sys/dev/acpi/apei_hestvar.h: revision 1.1 distrib/sets/lists/debug/module.md.i386: revision 1.10 sys/dev/acpi/apei_reg.c: revision 1.2 sys/dev/acpi/apei_reg.c: revision 1.3 sys/dev/acpi/apei_reg.h: revision 1.1 sys/dev/acpi/apei_reg.h: revision 1.2 sys/dev/acpi/apei_reg.h: revision 1.3 sys/dev/acpi/acpi_hed.c: revision 1.1 sys/dev/acpi/apei_einj.c: revision 1.1 sys/dev/acpi/apeivar.h: revision 1.1 sys/dev/acpi/apei_einj.c: revision 1.2 sys/dev/acpi/apei_einj.c: revision 1.3 sys/dev/acpi/apei_einj.c: revision 1.4 sys/dev/acpi/apei_einj.c: revision 1.5 share/man/man4/Makefile: revision 1.734 sys/dev/acpi/apei_einj.c: revision 1.6 sys/dev/acpi/apei_einj.c: revision 1.7 sys/dev/acpi/files.acpi: revision 1.131 sys/dev/acpi/files.acpi: revision 1.132 sys/dev/acpi/apei_interp.c: revision 1.1 sys/dev/acpi/apei_interp.c: revision 1.2 share/man/man4/acpihed.4: revision 1.1 sys/dev/acpi/apei_mapreg.c: revision 1.1 sys/dev/acpi/apei_interp.c: revision 1.3 share/man/man4/acpihed.4: revision 1.2 distrib/sets/lists/modules/md.i386: revision 1.98 sys/dev/acpi/apei_mapreg.c: revision 1.2 sys/dev/acpi/apei_interp.h: revision 1.1 sys/dev/acpi/apei_interp.c: revision 1.4 distrib/sets/lists/modules/md.i386: revision 1.99 sys/modules/acpihed/Makefile: revision 1.1 sys/dev/acpi/apei_mapreg.c: revision 1.3 sys/dev/acpi/apei_interp.h: revision 1.2 sys/arch/amd64/conf/ALL: revision 1.185 sys/dev/acpi/apei_mapreg.h: revision 1.1 sys/dev/acpi/apei_mapreg.c: revision 1.4 sys/arch/amd64/conf/ALL: revision 1.186 sys/dev/acpi/apei_erstvar.h: revision 1.1 sys/dev/acpi/apei_erst.c: revision 1.1 sys/dev/acpi/apei_erst.c: revision 1.2 sys/dev/acpi/apei_erst.c: revision 1.3 sys/arch/i386/conf/ALL: revision 1.516 share/man/man4/apei.4: revision 1.1 sys/arch/i386/conf/ALL: revision 1.517 share/man/man4/apei.4: revision 1.2 distrib/sets/lists/debug/module.md.amd64: revision 1.15 sys/modules/acpihed/acpihed.ioconf: revision 1.1 sys/dev/acpi/apei_hed.h: revision 1.1 distrib/sets/lists/debug/module.md.amd64: revision 1.16 sys/dev/acpi/apei_cper.h: revision 1.1 (all via patch) apei(4): New driver for ACPI Platform Error Interfaces. For now it is wired up only in x86 ALL kernels, and built as a module for x86 and Arm. Once it gets a little more testing on machines with APEI, I would like to flip it on by default. PR kern/58046 apei(4): Pacify -Wsign-compare. Assert that the parsing made forward progress too while here. PR kern/58046 apei(4): Tweak some comments about the APEI interpreter language. No functional change intended. PR kern/58046 apei(4): Fix parsing checks for TRIGGER_ERROR action table. The TableSize is size of the header plus the body, not just the body. PR kern/58046 apei(4): Note some TODOs for EINJ and HEST. No functional change intended, comments only. PR kern/58046 acpihed(4): New driver for PNP0C33 to notify apei(4). PNP0C33 denotes the ACPI Hardware Error Device, which exists only to be a vector for event notifications. PR kern/58046 acpihed(4): fix name in Dt, use Ql apei(4): Plug memory leak on teardown of instruction interpreter. PR kern/58046 apei(4): Fix indexing of multi-unit register access. PR kern/58046 apei(4): Fix register chunk counting. Now it will actually read and write the registers! Have been updating and reloading the wrong module to test this, oops. PR kern/58046 apei(4): Allow pre-mapping I/O registers too. PR kern/58046 apei(4): Pre-map registers when compiling interpreter. This way we don't have to worry about mapping them in nasty contexts where access to uvm_km_alloc may not be allowed. Paves the way to use ERST for saving dmesg on crash. Exception: ACPI_ERST_MOVE_DATA still needs to do AcpiOsMapMemory. We'll need to reserve a couple pages to avoid that. PR kern/58046 apei(4): Simplify EINJ/ERST register access now that it's pre-mapped. PR kern/58046 apei(4): Make sure to initialize *fatalp in apei_gesb_report. PR kern/58046 apei: fix typos in comments apei: fix typos in comments and snprintb bitfmt apei(4): Fix uninitialized stack access in error branch. PR kern/58046 apei(4), acpihed(4): Wire up man pages to build. PR kern/58046: Missing APEI (ACPI Platform Error Interface) support
Add debug info for new acpivmgenid module
distrib/sets/lists: Add a blank comment line between RCS id and body. This serves as a buffer between RCS id changes and other changes to the set lists, in an attempt to reduce the pain of merge conflicts around mass set list changes. No functional change intended.
acpihed(4): New driver for PNP0C33 to notify apei(4). PNP0C33 denotes the ACPI Hardware Error Device, which exists only to be a vector for event notifications. PR kern/58046
apei(4): New driver for ACPI Platform Error Interfaces. For now it is wired up only in x86 ALL kernels, and built as a module for x86 and Arm. Once it gets a little more testing on machines with APEI, I would like to flip it on by default. PR kern/58046
Pull up following revision(s) (requested by andvar in ticket #329): distrib/sets/lists/modules/md.amd64: revision 1.100 sys/external/bsd/drm2/dist/include/drm/drm_pciids.h: revision 1.5 sys/arch/amd64/conf/GENERIC: revision 1.605 sys/modules/Makefile: revision 1.279 distrib/sets/lists/debug/module.md.amd64: revision 1.14 viadrmums(4): build legacy VIA DRM UMS driver module for amd64. This driver is not built-in by default, thus loadable module can help (un)lucky owners of 64-bit capable VIA (Nano/Eden) systems or early AMD/Intel systems with some VIA chipsets, which include VIA integrated graphics. I also boldly added product IDs for few later models from VX8xx/VX9xx chipsets without 3D support (DX9_0) to "expand" the driver support to more systems. Tested successfully basic functionality on VX800, and partially successfully on VX900 (on VX900 Xorg failed to initialize due to openchrome related issues, viadrmums attaches and it is by used the driver). Didn't test on VX855, I don't have one.
viadrmums(4): build legacy VIA DRM UMS driver module for amd64. This driver is not built-in by default, thus loadable module can help (un)lucky owners of 64-bit capable VIA (Nano/Eden) systems or early AMD/Intel systems with some VIA chipsets, which include VIA integrated graphics. I also boldly added product IDs for few later models from VX8xx/VX9xx chipsets without 3D support (DX9_0) to "expand" the driver support to more systems. Tested successfully basic functionality on VX800, and partially successfully on VX900 (on VX900 Xorg failed to initialize due to openchrome related issues, viadrmums attaches and it is by used the driver). Didn't test on VX855, I don't have one. Pull up to netbsd-10 is needed.
Missed the compat_netbsd32_100 stuff in previous commit
drm: Hook up the drmkms modules to the build.
Revert editor mishap in r1.10
And, we're not ready for 10.0 yet, so remove a couple premature lines! Thanks, Rin!
remove duplicate entry and blank line that crept in from somewhere.
Oopppss, /usr has no `e' :)
Include debug files for new amdgpu modules
Disable drmkms module builds. They haven't been functional (and won't be before fixing genfb abi). In a new drm update, we haven't prioritized fixing the build either.
Sync with HEAD.
Move pad module to MI debug set lists
Update sets lists for new compat_netbsd32_coredump module
Add HAVE_NVMM and use it to control the build of NVMM related components. Defined to "yes" on amd64, "no" everywhere else.
Add if_iavf
Add module debug sets