aboutsummaryrefslogtreecommitdiff
path: root/sys/contrib
Commit message (Collapse)AuthorAgeFilesLines
...
* | Explicit CTLFLAG_DYN not neededRyan Moeller2020-10-041-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | Dynamically created OIDs automatically get this flag set. Reviewed by: jhb MFC after: 1 week Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D26561 Notes: svn path=/head/; revision=366433
* | OpenZFS: don't call fpu_kern_thread on i386Matt Macy2020-10-021-1/+1
| | | | | | | | Notes: svn path=/head/; revision=366353
* | OpenZFS: MFV 2.0-rc3-gfc5966Matt Macy2020-10-0153-495/+1340
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Annotate FreeBSD sysctls with CTLFLAG_MPSAFE - Reduce stack usage of Lua - Don't save user FPU context in kernel threads - Add support for procfs_list - Code cleanup in zio_crypt - Add DB_RF_NOPREFETCH to dbuf_read()s in dnode.c - Drop references when skipping dmu_send due to EXDEV - Eliminate gratuitous bzeroing in dbuf_stats_hash_table_data - Fix legacy compat for platform IOCs Notes: svn path=/head/; revision=366350
* | Continued ipfilter #ifdef cleanup. The r343701 log entry contains aCy Schubert2020-09-301-4/+3
| | | | | | | | | | | | | | | | | | complete description. MFC after: 1 week Notes: svn path=/head/; revision=366287
* | ZFS: Fix a logic bug in the FreeBSD getpages VOPMark Johnston2020-09-291-2/+4
| | | | | | | | | | | | | | | | | | | | | | This was introduced when I merged r361287 to OpenZFS and has been fixed there already, commit 3f6bb6e43fd68e. Reported by: swills Reviewed by: allanjude, freqlabs, mmacy Notes: svn path=/head/; revision=366252
* | Remove extraneous bracket.Cy Schubert2020-09-271-1/+1
| | | | | | | | | | | | | | MFC after: 3 days Notes: svn path=/head/; revision=366204
* | cache: drop the force flag from purgevfsMateusz Guzik2020-09-231-1/+1
| | | | | | | | | | | | | | | | | | The optional scan is wasteful, thus it is removed altogether from unmount. Callers which always want it anyway remain unaffected. Notes: svn path=/head/; revision=366071
* | vchi: rename bitset macros to avoid collision with bitset(9)D Scott Phillips2020-09-212-15/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | An upcoming change to include bitset(9) macros from vm_page.h causes a macro name collision with vchi's custom bitset macros. This change was performed mechanically by: sed -i .orig s/BITSET/VCHI_BITSET/g $(grep -rl BITSET sys/contrib/vchiq) Reviewed by: andrew Approved by: scottl (implicit) MFC after: 1 week Sponsored by: Ampere Computing, Inc. Differential Revision: https://reviews.freebsd.org/D26177 Notes: svn path=/head/; revision=365974
* | MFV 2.0-rc2Matt Macy2020-09-18134-524/+2671
| | | | | | | | | | | | | | | | - Fixes divide by zero for unusual hz - remove cryptodev dependency Notes: svn path=/head/; revision=365894
* | ys/contrib/dev/ath: remove unintentional double semicolonEd Maste2020-09-181-1/+1
| | | | | | | | | | | | | | Approved by: adrian Notes: svn path=/head/; revision=365888
* | Do not copy vp into f_data for DTYPE_VNODE files.Konstantin Belousov2020-09-151-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The pointer to vnode is already stored into f_vnode, so f_data can be reused. Fix all found users of f_data for DTYPE_VNODE. Provide finit_vnode() helper to initialize file of DTYPE_VNODE type. Reviewed by: markj (previous version) Discussed with: freqlabs (openzfs chunk) Tested by: pho (previous version) Sponsored by: The FreeBSD Foundation Differential revision: https://reviews.freebsd.org/D26346 Notes: svn path=/head/; revision=365783
* | ice_ddp: Fix 1.3.16.0 packageEric Joyner2020-09-101-0/+0
| | | | | | | | | | | | | | | | | | | | | | The version uploaded in the previous commit was far too small. This one should be the right size. MFC after: 1 day Sponsored by: Intel Corporation Notes: svn path=/head/; revision=365550
* | ZFS: MFV 2.0-rc1-gfd20a8Matt Macy2020-09-0455-578/+711
| | | | | | | | | | | | | | | | | | | | - fixes jail delegation - fixes raw kstat unsupported complaints - exposes dbgmsg, dbuf, and checksum benchmark stats - restore rename -u support Notes: svn path=/head/; revision=365347
* | ice_ddp: Update package file to 1.3.16.0Eric Joyner2020-09-043-1/+2221
| | | | | | | | | | | | | | | | | | | | | | This package is intended to be used with ice(4) version 0.26.16. That update will happen in a forthcoming commit. MFC after: 3 days Sponsored by: Intel Corporation Notes: svn path=/head/; revision=365332
* | ZFS: MFV 2.0-rc1-ga00c61Matt Macy2020-08-2843-80/+320
| | | | | | | | Notes: svn path=/head/; revision=364930
* | remove pragma ident linesToomas Soome2020-08-267-14/+0
| | | | | | | | | | | | | | | | | | The #pragma ident is historical relict and not needed any more, this pragma is actually unknown for common compilers and is only causing trouble. Notes: svn path=/head/; revision=364806
* | Initial import from vendor-sys branch of openzfsMatt Macy2020-08-243671-0/+770607
| | | | | | | | Notes: svn path=/head/; revision=364740
* | pcg-c: Add 'static' to inline function definitionsConrad Meyer2020-08-151-238/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make the inlines static to avoid kernel build failure with Clang 11 on i386. (The issue was not observed with Clang 10, currently in tree; reproduction depends on compiler inlining choices.) The compiler may choose not to inline 'bare' C inlines, and in that case expects a symbol of the same name will be available. It does not automatically define that symbol at use, because of traditional C linking semantics. (In contrast, C++ does define it, and then deduplicates redundant definitions at link). As we do not instantiate the C99 inline ('extern inline ...;'), the linker errors with "undefined symbol." Reported by: dim Tested by: dim Fixes: r364219 Notes: svn path=/head/; revision=364260
* | Add prng(9) APIConrad Meyer2020-08-131-31/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add prng(9) as a replacement for random(9) in the kernel. There are two major differences from random(9) and random(3): - General prng(9) APIs (prng32(9), etc) do not guarantee an implementation or particular sequence; they should not be used for repeatable simulations. - However, specific named API families are also exposed (for now: PCG), and those are expected to be repeatable (when so-guaranteed by the named algorithm). Some minor differences from random(3) and earlier random(9): - PRNG state for the general prng(9) APIs is per-CPU; this eliminates contention on PRNG state in SMP workloads. Each PCPU generator in an SMP system produces a unique sequence. - Better statistical properties than the Park-Miller ("minstd") PRNG (longer period, uniform distribution in all bits, passes BigCrush/PractRand analysis). - Faster than Park-Miller ("minstd") PRNG -- no division is required to step PCG-family PRNGs. For now, random(9) becomes a thin shim around prng32(). Eventually I would like to mechanically switch consumers over to the explicit API. Reviewed by: kib, markj (previous version both) Discussed with: markm Differential Revision: https://reviews.freebsd.org/D25916 Notes: svn path=/head/; revision=364219
* | Import PCG-C into sys/contribConrad Meyer2020-07-301-0/+2544
| | | | | | | | | | | | | | | | The intended (future) use is to provide fast pseudo-random numbers in non- cryptographic applications. Notes: svn path=/head/; revision=363720
* | MFV: r363292Jung-uk Kim2020-07-1811-19/+80
|\| | | | | | | | | | | | | Merge ACPICA 20200717. Notes: svn path=/head/; revision=363300
* | Fix incorrect byte order in ipfstat -f output.Cy Schubert2020-07-172-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | - make sure frag is initialized to 0 - initialize ipfr_p field NetBSD PR: 55137 Submitted by: christos@NetBSD.org Reported by: christos@NetBSD.org Obtained from: NetBSD fil.c r1.32, ip_frag.c r1.8 MFC after: 2 weeks Notes: svn path=/head/; revision=363285
* | pfil_run_hooks() can be called recursively, so we have toCy Schubert2020-07-171-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | define FASTROUTE_RECURSION in fil.c Submitted by: christos@NetBSD.org Reported by: christos@NetBSD.org Obtained from: NetBSD r1.31 MFC after: 2 weeks Notes: svn path=/head/; revision=363284
* | Rename nvpair.c to bsd_nvpair.c to not conflict with openzfs' version.Matt Macy2020-06-271-0/+0
| | | | | | | | Notes: svn path=/head/; revision=362666
* | Document upgrade procedure in FREEBSD-upgradeMitchell Horne2020-06-041-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | It was pointed out to me that this is the convention for documenting upgrade instructions, rather than just leaving the instructions in the commit message. It's possible these commands won't be used again before we transition to git, but then at least they'll give a path forward for whoever touches this next. Suggested by: lwhsu Notes: svn path=/head/; revision=361807
* | Update edk2 headers to stable202005Mitchell Horne2020-06-0437-2874/+2134
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We use these to compile libefivar. The particular motivation for this update is the inclusion of the RISC-V machine definitions that allow us to build the library on the platform. This support could easily have been submitted as a small local diff, but the timing of the release coincided with this work, and it has been over 3 years since these sources were initially imported. Note that this comes with a license change from regular BSD 2-clause to the BSD+Patent license. This has been approved by core@ for this particular project [1]. As with the original import, we retain only the subset of headers that we actually need to build libefivar. I adapted imp@'s process slightly for this update: # Generate list of the headers needed to build cp -r ../vendor/edk2/dist/MdePkg/Include sys/contrib/edk2 cd lib/libefivar make pushd `make -V .OBJDIR` cat .depend*.o | grep sys/contrib | cut -d' ' -f 3 | sort -u | sed -e 's=/full/path/sys/contrib/edk2/==' > /tmp/xxx popd # Merge the needed files cd ../../sys/contrib/edk2 svn revert -R . for i in `cat /tmp/xxx`; do svn merge -c VendorRevision svn+ssh://repo.freebsd.org/base/vendor/edk2/dist/MdePkg/$i $i done svn merge -c VendorRevision svn+ssh://repo.freebsd.org/base/vendor/edk2/dist/MdePkg/MdePkg.dec MdePkg.dec [1] https://www.freebsd.org/internal/software-license.html Notes: svn path=/head/; revision=361802
* | MFV: r361597Jung-uk Kim2020-05-2811-18/+97
|\| | | | | | | | | | | | | Import ACPICA 20200528. Notes: svn path=/head/; revision=361600
* | ice(4): Introduce new driver for Intel E800 Ethernet controllersEric Joyner2020-05-263-0/+238
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ice(4) driver is the driver for the Intel E8xx series Ethernet controllers; currently with codenames Columbiaville and Columbia Park. These new controllers support 100G speeds, as well as introducing more queues, better virtualization support, and more offload capabilities. Future work will enable virtual functions (like in ixl(4)) and the other functionality outlined above. For full functionality, the kernel should be compiled with "device ice_ddp" like in the amd64 NOTES file, and/or ice_ddp_load="YES" should be added to /boot/loader.conf so that the DDP package file included in this commit can be downloaded to the adapter. Otherwise, the adapter will fall back to a single queue mode with limited functionality. A man page for this driver will be forthcoming. MFC after: 1 month Relnotes: yes Sponsored by: Intel Corporation Differential Revision: https://reviews.freebsd.org/D21959 Notes: svn path=/head/; revision=361541
* | Adjust ENA driver to the new HALMarcin Wojtas2020-05-2610-582/+525
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Removed adaptive interrupt moderation (not suported on FreeBSD). * Use ena_com_free_q_entries instead of ena_com_free_desc. * Don't use ENA_MEM_FREE outside of the ena_com. * Don't use barriers before calling doorbells as it's already done in the HAL. * Add function that generates random RSS key, common for all driver's interfaces. * Change admin stats sysctls to U64. Submitted by: Michal Krawczyk <mk@semihalf.com> Obtained from: Semihalf Sponsored by: Amazon, Inc. Notes: svn path=/head/; revision=361511
* | [ath] [ath_hal] Propagate the HAL_RESET_TYPE through to the chip reset; set ↵Adrian Chadd2020-05-253-5/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | it during ath_reset() Although I added the reset type field to ath_hal_reset() years ago, I never finished adding it both throughout the HALs and in if_ath.c. This will eventually deprecate the ath_hal force_full_reset option because it can be requested at the driver layer. So: * Teach ar5416ChipReset() and ar9300_chip_reset() about the HAL type * Use it in ar5416Reset() and ar9300_reset() when doing a full chip reset * Extend ath_reset() to include the HAL_RESET_TYPE parameter added in the above functions * Use HAL_RESET_NORMAL in most calls to ath_reset() * .. but use HAL_RESET_BBPANIC for the BB panics, and HAL_RESET_FORCE_COLD during fatal, beacon miss and other hardware related hangs. This should be a glorified no-op outside of actual hardware issues. I've tested things with ath_hal force_full_reset set to 1 for years now, so I know that feature and a full reset works (albeit much slower than a warm reset!) and it does unwedge hardware. The eventual aim is to use this for all the places where the driver detects a potential hang as well as if long calibration - ie, noise floor calibration - fails to complete. That's one of the big hardware related things that causes station mode operation to hang without easy recovery. Differential Revision: https://reviews.freebsd.org/D24981 Notes: svn path=/head/; revision=361486
* | Unbreak ARM64 kernel build after r361426Conrad Meyer2020-05-231-3/+3
| | | | | | | | | | | | | | X-MFC-With: r361426 Notes: svn path=/head/; revision=361427
* | Update to Zstandard 1.4.5Conrad Meyer2020-05-23292-37340/+5670
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As usual, the full release notes are found on Github: https://github.com/facebook/zstd/releases/tag/v1.4.5 Notable changes include: * Improved decompress performance on amd64 and arm (5-10% and 15-50%, respectively). * '--patch-from' zstd(1) CLI option, which provides something like a very fast version of bspatch(1) with slightly worse compression. See release notes. In this update, I dropped the 3-year old -O0 workaround for an LLVM ARM bug; the bug was fixed in LLVM SVN in 2017, but we didn't remove this workaround from our tree until now. MFC after: I won't, but feel free Relnotes: yes Notes: svn path=/head/; revision=361426
* | contrib/zstd: Revise Xlist for 1.4.5 importConrad Meyer2020-05-231-3/+3
| | | | | | | | Notes: svn path=/head/; revision=361425
* | [ath_hal_ar9300] Ensure AH_BYTE_ORDER is defined before used.Adrian Chadd2020-05-1210-0/+51
| | | | | | | | | | | | | | Same deal here - ensure endian bits are set here first! Notes: svn path=/head/; revision=360954
* | [ath_hal] [ath_hal_ar9300] Fix endian macros to work in and out of kernel tree.Adrian Chadd2020-05-122-13/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Yes, people shouldn't use bitfields in C for structure parsing. If someone ever wants a cleanup task then it'd be great to remove them from this vendor code and other places in the ar9285/ar9287 HALs. Alas, here we are. AH_BYTE_ORDER wasn't defined and neither were the two values it could be. So when compiling ath_ee_print_9300 it'd default to the big endian struct layout and get a WHOLE lot of stuff wrong. So: * move AH_BYTE_ORDER into ath_hal/ah.h where it can be used by everyone. * ensure that AH_BYTE_ORDER is actually defined before using it! This should work on both big and little endian platforms. Notes: svn path=/head/; revision=360953
* | [ar9300] Disable unconditionally reducing transmit power in the case of FCC.Adrian Chadd2020-05-112-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Ok, yeah, the commit title is a bit misleading. This has to do with CDD (cyclic delay diversity) - how this and later wifi hardware transmits lower rates over more antennas. Eg, if you're transmitting legacy 11abg rates on 2 or 3 antennas, you COULD just send them all at the same time or you could delay each by tens/hundreds of nanoseconds to try and get some better diversity characteristics. However, this has a fun side effect - the antenna pattern is no longer a bunch of interacting dipoles, but are a bunch of interacting dipoles plus a bunch of changing phases. And it's frequency dependent - 50-200nS is not exactly the same fraction of a wavelength across all of 2GHz or 5GHz! Thus the power spectral density and maximum directional gain that you're effectively getting is not .. well, as flat as it once was. For more information, look up FCC/OET 13TR1003 in the FCC technical report database. It has pretty graphics and everything. Anyway, the problem lies thusly - the CDD code just subtracts another 3dB or 5dB for the lower rates based on transmit antenna configuration. However, it's not done based on operating configuration and it doesn't take into account how far from any regulatory limits the hardware is at. It also doesn't let us do things like transmit legacy rates and frames on a single antenna without losing up to 5dB when we absolutely don't need to in that case (there's no CDD used when one antenna is used!) This shows up as the hardware behaving even worse for longer distance links at 20MHz because, well, those are the exact rates losing a bunch more transmit power. * For lower power NICs (ie the majority of what is out there!) it's highly unlikely we're going to hit anywhere near the PSD limits. * It's doing it based on the existing limits from the CTL table (conformance testing limits) - this isn't the regulatory max! It's what the NIC is allowed to put out in each frequency and rate configuration! So things like band edges, power amplifier behaviour and maximum current draw apply here. Blindly subtracting 3 to 5dB from /this/ value is /very/ conservative.. * /and/ ath9k just plainly doesn't do any of this at all. So, for now disable it and get the TX power back, thus matching what ath9k in Linux is doing. If/once I get some more cycles I'll look at making it a bit more adaptive and really only kick in if we're a few dB away from hard regulatory limits. Tested: * AR9344 (2GHz + SoC, 2x2 configuration) - AP and STA modes * QCA9580 (5GHz 2x2 and 3x3 configurations) - AP and STA modes Notes: svn path=/head/; revision=360888
* | MFV: r360512Jung-uk Kim2020-05-0117-74/+307
|\| | | | | | | | | | | | | Merge ACPICA 20200430. Notes: svn path=/head/; revision=360517
* | Convert ipfilter to the new routing KPI.Cy Schubert2020-04-191-8/+13
| | | | | | | | | | | | | | Reviewed by: melifaro (previous version) Notes: svn path=/head/; revision=360101
* | fib4_free_nh_ext is an empty function. It does nothing. Don't call it.Cy Schubert2020-04-191-5/+0
| | | | | | | | | | | | | | MFC after: 2 weeks Notes: svn path=/head/; revision=360100
* | Remove FreeBSD/armv4 specific bits from CK.Olivier Houchard2020-04-132-354/+0
| | | | | | | | | | | | | | | | | | Now that armv4/v5 is gone, remove the bits that implemented atomic operations by disabling interrupts. Those were specific to FreeBSD and never reached upstream. Notes: svn path=/head/; revision=359909
* | Merge ACPICA 20200326.Jung-uk Kim2020-03-2738-85/+511
|\| | | | | | | Notes: svn path=/head/; revision=359346
* | Fix misleading indentation warning in OCTEON1 kernelAlex Richardson2020-03-171-3/+4
| | | | | | | | | | | | | | | | | | | | This is required to switch MIPS to compile with LLVM by default (D23204). Reviewed By: brooks Differential Revision: https://reviews.freebsd.org/D24091 Notes: svn path=/head/; revision=359034
* | Retire macros:Cy Schubert2020-03-023-8/+5
| | | | | | | | | | | | | | | | | | | | | | BSD_GE_YEAR BSD_GT_YEAR BSD_LT_YEAR MFC after: 3 days Notes: svn path=/head/; revision=358560
* | Remove the now unused FREEBSD_GE_REV, FREEBSD_GT_REV, and FREEBSD_LT_REVCy Schubert2020-03-021-6/+0
| | | | | | | | | | | | | | | | | | macros. MFC after: 3 days Notes: svn path=/head/; revision=358559
* | Continuing the effort started in r343701, #ifdef cleanup, checking forCy Schubert2020-03-025-7/+6
| | | | | | | | | | | | | | | | | | __FreeBSD_version > 3.0 and 5.0 is redundant. MFC after: 3 days Notes: svn path=/head/; revision=358558
* | With the planned removal of GIANT (sysctl uses GIANT), make future-proofCy Schubert2020-02-261-6/+10
| | | | | | | | | | | | | | | | | | | | ipfilter by making it sysctl locking mpsafe. Reviewed by: kaktus Differential Revision: https://reviews.freebsd.org/D23839 Notes: svn path=/head/; revision=358356
* | Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (17 of many)Pawel Biernacki2020-02-261-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes. This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags. Mark all obvious cases as MPSAFE. All entries that haven't been marked as MPSAFE before are by default marked as NEEDGIANT Approved by: kib (mentor, blanket) Commented by: kib, gallatin, melifaro Differential Revision: https://reviews.freebsd.org/D23718 Notes: svn path=/head/; revision=358333
* | [PowerPC] [Book-E] Remove obsolete interrupt binding workaroundBrandon Bergren2020-02-252-33/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove an old workaround that is no longer necessary since rS343824. There used to be a problem with FMan interrupts firing on multiple CPUS at the same time. This ended up being due to multicast interrupts being unsupported in the Freescale PIC (so instead of using a selection algorithm, it would do some unspecified action, such as interrupting multiple cpus at random.) Reviewed by: jhibbits Sponsored by: Tag1 Consulting, Inc. Differential Revision: https://reviews.freebsd.org/D23829 Notes: svn path=/head/; revision=358322
* | [PowerPC] [Book-E] Fix dpaa interrupt binding.Brandon Bergren2020-02-252-14/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After the network epoch was added, we lost the ability to migrate the ithread in the middle of dispatch, as being in the network epoch will pin the current thread (for safety reasons.) Luckily, we don't actually have to do this workaround in the first place, as we can just bind it to the correct cpu when we preallocate it. Pass dev through to XX_PreallocAndBindIntr() and actually bind it to the cpu like it was supposed to in the first place, instad of leaving it floating and moving it to the correct cpu the first time it fires. This fixes panics while bringing up dtsec on my X5000. Reviewed by: jhibbits Sponsored by: Tag1 Consulting, Inc. Differential Revision: https://reviews.freebsd.org/D23826 Notes: svn path=/head/; revision=358307
* | Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (8 of many)Pawel Biernacki2020-02-241-11/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes. This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags. Approved by: kib (mentor, blanket) Differential Revision: https://reviews.freebsd.org/D23628 Notes: svn path=/head/; revision=358276
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-16 11:17:11 +0000