aboutsummaryrefslogtreecommitdiff
path: root/sys/conf
Commit message (Collapse)AuthorAgeFilesLines
* Add UPDATING entries and bump versionrelease/14.4.0-p1releng/14.4Philip Paeps2026-03-251-1/+1
| | | | Approved by: so
* Update in preparation for 14.4-RELEASErelease/14.4.0Colin Percival2026-03-061-1/+1
| | | | | | | | | - Bump BRANCH to RELEASE - Add the anticipated RELEASE announcement date - Set a static __FreeBSD_version Approved by: re (implicit) Sponsored by: OpenSats Initiative
* 14.4: Update to RC1Colin Percival2026-02-271-1/+1
| | | | | Approved by: re (implicit) Sponsored by: OpenSats Initiative
* 14.3: Update to BETA3Colin Percival2026-02-201-1/+1
| | | | | Approved by: re (implicit) Sponsored by: OpenSats Initiative
* 14.3: Update to BETA2Colin Percival2026-02-131-1/+1
| | | | | Approved by: re (implicit) Sponsored by: OpenSats Initiative
* 14.4: create releng/14.4 branchColin Percival2026-02-061-1/+1
| | | | | | | | | Update from PRERELEASE to BETA1 Switch pkg(8) configuration to use the quarterly repository Bump __FreeBSD_version Approved by: re (implicit) Sponsored by: OpenSats Initiative
* METALOG: Order keyword entriesJose Luis Duran2026-02-031-1/+1
| | | | | | | | | | | | | To facilitate comparison with mtree -C generated output, keep the keywords ordered. No functional change intended. Reviewed by: imp MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D54872 (cherry picked from commit fe962e33d86f888b496b17251c8bedebf92be8ee)
* vchiq: fix build with clang 21Dimitry Andric2026-01-262-1/+4
| | | | | | | | | | | | | | | | | | | | When compiling vchiq with clang 21, the following -Werror warning is produced: sys/contrib/vchiq/interface/vchiq_arm/vchiq_arm.c:728:27: error: default initialization of an object of type 'VCHIQ_QUEUE_MESSAGE32_T' with const member leaves the object uninitialized [-Werror,-Wdefault-const-init-field-unsafe] 728 | VCHIQ_QUEUE_MESSAGE32_T args32; | ^ sys/contrib/vchiq/interface/vchiq_arm/vchiq_ioctl.h:151:40: note: member 'elements' declared 'const' here 151 | const /*VCHIQ_ELEMENT_T * */ uint32_t elements; | ^ While the warning is formally correct, the 'args32' object is immediately initialized after its declaration. Therefore, suppress the warning. MFC after: 3 days (cherry picked from commit b39662fc388678db2b7b5fa3c900205252d15b3b)
* 14.4: Update stable/14 to -PRERELEASEColin Percival2026-01-231-2/+2
| | | | | | | | | | | | | This marks the start of the FreeBSD 14.4 release cycle; the stable/14 tree is now in "code slush". Developers are encouraged to prioritize fixing bugs (and/or merging bug fixes from HEAD) over new features at this time. Commit approval from re@ is not required but if new features introduce problems they may be removed from the release. Approved by: re (implicit) Sponsored by: OpenSats Initiative
* arm64: Add a new CPU feature frameworkAndrew Turner2026-01-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This will be used to enable features that are discoverable on boot. It has support to check if a feature needs to be enabled, and if there is any errata associated with the feature that mean it shouldn't be enabled. It can also be used to enable errata workarounds that aren't associated with a specific feature, e.g. where we need to trap access to a register in userspace to emulate it. As some features need to be enabled early, while others can wait there are two options for when to enable a feature: * CPU_FEAT_EARLY_BOOT: The feature will be enabled early in the boot. On the boot CPU this is in initarm, while on secondary CPUs this is before signalling the CPU has started. * CPU_FEAT_AFTER_DEV: The feature will be enabled after devices have attached but before interrupts are enabled. There are also two scopes for where to enable the feature: * CPU_FEAT_PER_CPU: The feature will be checked and enabled on all CPU cores. * CPU_FEAT_SYSTEM: The feature will only be checked and enabled on a single core. It is expected the former will be used for most features, while the latter is for features that set a global variable to be checked. Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D47812 (cherry picked from commit ac4fa5838bb33f0c3ba05fce02d41164bd84a560)
* ipfilter: Disable ipfs(8) by defaultCy Schubert2026-01-052-0/+2
| | | | | | | | | | | | | | | At the moment ipfs(8) is a tool that can be easily abused. Though the concept is sound the implementation needs some work. ipfs(8) should be considered experimental at the moment. This commit also makes ipfs support in the kernel optional. Reviewed by: emaste, glebius MFC after: 1 week Differential revision: https://reviews.freebsd.org/D53787 (cherry picked from commit 0ff0c19e7f70bc4d3f98196a8ad43de635cf13e5)
* kmod.mk: Remove a trailing reference to pccarddevs.hJohn Baldwin2025-12-181-1/+1
| | | | | Fixes: 31b35400cf77 ("pccard: Remove more of the PC Card infrastructure") (cherry picked from commit 6bf611ada21216aefcd830ba71fbf0b5d776ea47)
* ipfw: Retire obsolete compat codeEd Maste2025-11-201-1/+0
| | | | | | | | | | | | | | | | | The current IPFW version 3 dates to 2010 (commit cc4d3c30ea28, "Bring in the most recent version of ipfw and dummynet, developed"). The compat code for FreeBSD 8 and earlier has a number of issues and is no longer needed, so remove it. Reported by: Ilja Van Sprundel <ivansprundel@ioactive.com> Reviewed by: ae, glebius Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D53343 (cherry picked from commit c59aab9a5b3970b3ccec744f759e6cb87e938dbe) (cherry picked from commit 9657c50cdd7741404d99881fdd9243175086ede1)
* ix/ixv: Add support for new Intel Ethernet E610 family devicesBhosale, Yogeshnull2025-10-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is part 1 of the support for the new Intel Ethernet E610 family of devices. Introduce new PCI device IDs: • 57AE: Intel(R) E610 (Backplane) • 57AF: Intel(R) E610 (SFP) • 57B0: Intel(R) E610 (10 GbE) • 57B1: Intel(R) E610 (2.5 GbE) • 57B2: Intel(R) E610 (SGMII) Key updates for E610 family: • Firmware manages Link and PHY • Implement new CSR-based Admin Command Interface (ACI) for SW-FW interaction • Tested exclusively for x64 operating systems on E610-XT2/XT4 (10G) and E610-IT4 (2.5G) • Enable link speeds above 1G: 2.5G, 5G and 10G • NVM Recovery Mode and Rollback support Signed-off-by: Yogesh Bhosale yogesh.bhosale@intel.com Co-developed-by: Krzysztof Galazka krzysztof.galazka@intel.com Approved by: kbowling (mentor), erj (mentor) Tested by: gowtham.kumar.ks_intel.com Sponsored by: Intel Corporation MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D50067 (cherry picked from commit dea5f973d0c8d29a79b433283d0a2de8f4615957)
* sys: NOTES, GENERIC*: Re-order 'wlan_tkip'Olivier Certner2025-10-101-2/+2
| | | | | | | | | | | | | | | | | | | Re-order the devices in order of appearance of the related technologies, so 'wlan_tkip' before 'wlan_ccmp'. No functional change (intended). Reviewed by: adrian, emaste Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D52444 (cherry picked from commit c1eff1d745a1193c199f735733e376161c69b12c) The original commit has been modified not to include the changes related to 'wlan_gcmp', which are not in stable/14. The original commit message above was reworked to reflect the actual commit content.
* newvers: Add a builddir parameterMark Johnston2025-09-302-3/+7
| | | | | | | | | | | | | | When reproducible builds are configured, we should use /usr/obj as the canonical objdir. Add a parameter to newvers.sh to ensure that build metadata is reproducible. Reviewed by: emaste MFC after: 1 month Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D50954 (cherry picked from commit 3238878379d3bd4bb9796ccb41c090139bbde94f)
* sys/conf: Remap paths for reproducibilityMark Johnston2025-09-302-4/+36
| | | | | | | | | | | | | | | | | | | As in bsd.lib.mk and bsd.prog.mk, we need to remap paths in the kernel and in kernel modules when reproducible builds are configured. Add directives to kern.post.mk and kmod.mk to remap the src, obj and sysroot dirs. For the sysroot, we need to pass the value of the SYSROOT variable to the kernel makefiles, which involves changing Makefile.inc1. In so doing I reverted a portion of commit 35fb812adfc21; I can't see any harm in passing the SYSROOT variable down. MFC after: 1 month Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D50953 (cherry picked from commit eebadc7d8590ff8d38fdbcfd90651c931e713648)
* tcp: improve compilation of cc and their helper modulesMichael Tuexen2025-09-221-5/+13
| | | | | | | | | | | | | | | | | * Allow the congestion control modules CDG, CHD, HD, and vegas also to be compiled into the kernel for IPv6 only kernel configs. * Compile the helper module h_ertt for round trip time estimation only into the kernel, if one of the congestion control module using it (one of CDG, CDH, HD, or vegas) is also compiled into the kernel. Please note the second point implies that TCP TSO is done whenever possible as long as none of the congestion control modules CDG, CHD, HD, or vegas is loaded or compiled into the kernel. Reviewed by: cc Sponsored by: Netflix, Inc. Differential Revision: https://reviews.freebsd.org/D52547 (cherry picked from commit 1bb72d3d6eee50232b6d6acbc201f9aaac93e2b5)
* vdso: Build without debug infoMark Johnston2025-09-211-2/+2
| | | | | | | | | | | | | | | The debug info is not very useful and embeds build paths because elf-vdso.so.o is built without CFLAGS, breaking reproducibility of elf-vdso.so.o and thus the kernel. Just stop passing debug flags to amd64_vdso.sh. Reviewed by: kib MFC after: 2 weeks Sponsored by: Klara, Inc. Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D52129 (cherry picked from commit b7e0373acb1d022e9e5acb5be9727def5f941194)
* src.sys.mk: Support src.conf in SRCTOPDag-Erling Smørgrav2025-09-161-0/+4
| | | | | | | | | | | | | | | | If SRCCONF is not defined and src.conf exists at the top level of the source tree, use that instead of /etc/src.conf. MFC after: 3 days Reviewed by: kevans, imp Differential Revision: https://reviews.freebsd.org/D52470 (cherry picked from commit dd8c666d8b78f6b9ddb691f0505837fa885ff3b4) UPDATING: mention the src.conf change Fixes: dd8c666d8b78 ("src.sys.mk: Support src.conf in SRCTOP") (cherry picked from commit ab2fea3f9a5a58f0ba90499ad3a8614e3dca0c5f)
* NOTES: Fix whitespace in "options MAC_DO"Olivier Certner2025-09-121-1/+1
| | | | | | | | | | | | | For "options", we put a space before a TAB so that commenting out an option doesn't move the columns. No functional change. Fixes: c8d8cac2a847 ("mac_do(4): allow compiling into kernel") MFC after: 3 days Sponsored by: The FreeBSD Foundation (cherry picked from commit 1cf67b587023af90f2b2c6e87d9103ec42b2b9b2)
* jail: Add meta and env parametersIgor Ostapenko2025-09-111-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Each one is an arbitrary string associated with a jail. It can be set upon jail creation or added/modified later: > jail -cm ... meta="tag1=value1 tag2=value2" env="configuration" The values are not inherited from the parent jail. A parent jail can read both metadata parameters, while a child jail can read only env via security.jail.env sysctl. The maximum size of meta or env per jail is controlled by the global security.jail.meta_maxbufsize sysctl. Decreasing it does not alter the existing meta information. Each metadata buffer can be handled as a set of key=value\n strings: > jail -cm ... meta="$(echo k1=v1; echo k2=v2)" env.1=one > jls meta.k2 env.1 meta.k1 While meta.k1= resets the value to an empty string, the meta.k1 without the equal sign removes the given key. Relnotes: yes Reviewed by: jamie Tested by: dch Sponsored by: SkunkWerks GmbH Differential Revision: https://reviews.freebsd.org/D47668 (cherry picked from commit 30e6e008bc06385a66756bebb41676f4f9017eca)
* kern.post.mk: Support flavors in PORTS_MODULESDag-Erling Smørgrav2025-08-141-2/+8
| | | | | | | | | MFC after: 1 week PR: 288596 Reviewed by: pkubaj Differential Revision: https://reviews.freebsd.org/D51833 (cherry picked from commit 988426e815c12a899c8c6853090b8c8fca7ed5cd)
* sys/conf: Re-add -Wno-unused to ipfilter build flagsMark Johnston2025-08-131-1/+1
| | | | | | | | | This is still required on stable/14 because of the RCS tags defined at the top of each source file. This is a direct commit to stable/14. Fixes: 0947920999dc ("files: add new IPFILTER_C rule for netpfil/ipfilter sources")
* files: add new IPFILTER_C rule for netpfil/ipfilter sourcesSiva Mahadevan2025-08-102-36/+22
| | | | | | | | | This re-enables all compiler warnings for these sources. Pull Request: https://github.com/freebsd/freebsd-src/pull/1677 MFC after: 1 month (cherry picked from commit 45730dd3ed334d265fc77cf6df1f82013fd5bf69)
* Add an implementation of the 9P filesystemDoug Rabson2025-07-042-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is derived from swills@ fork of the Juniper virtfs with many changes by me including bug fixes, style improvements, clearer layering and more consistent logging. The filesystem is renamed to p9fs to better reflect its function and to prevent possible future confusion with virtio-fs. Several updates and fixes from Juniper have been integrated into this version by Val Packett and these contributions along with the original Juniper authors are credited below. To use this with bhyve, add 'virtio_p9fs_load=YES' to loader.conf. The bhyve virtio-9p device allows access from the guest to files on the host by mapping a 'sharename' to a host path. It is possible to use p9fs as a root filesystem by adding this to /boot/loader.conf: vfs.root.mountfrom="p9fs:sharename" for non-root filesystems add something like this to /etc/fstab: sharename /mnt p9fs rw 0 0 In both examples, substitute the share name used on the bhyve command line. The 9P filesystem protocol relies on stateful file opens which map protocol-level FIDs to host file descriptors. The FreeBSD vnode interface doesn't really support this and we use heuristics to guess the right FID to use for file operations. This can be confused by privilege lowering and does not guarantee that the FID created for a given file open is always used for file operations, even if the calling process is using the file descriptor from the original open call. Improving this would involve changes to the vnode interface which is out-of-scope for this import. Differential Revision: https://reviews.freebsd.org/D41844 Reviewed by: kib, emaste, dch MFC after: 3 months Co-authored-by: Val Packett <val@packett.cool> Co-authored-by: Ka Ho Ng <kahon@juniper.net> Co-authored-by: joyu <joyul@juniper.net> Co-authored-by: Kumara Babu Narayanaswamy <bkumara@juniper.net> (cherry picked from commit e97ad33a89a78f55280b0485b3249ee9b907a718)
* qat: add disable safe dc mode for QAT SPR devicesHareshx Sankar Raj2025-06-202-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Build and sysctl configuration modes are introduced for QAT SPR devices to disable safe dc mode. A new QAT driver build option ‘QAT_DISABLE_SAFE_DC_MODE’ is required to build the QAT driver with code that allows a request to be sent to FW to override the ‘History Buffer’ mitigation. Default QAT driver builds do not include this ‘QAT_DISABLE_SAFE_DC_MODE’ build option. Even if the QAT driver was built with code that allows a request to be sent to FW to override the ‘History Buffer’ mitigation, the QAT driver must still be configured using sysctl to request an override of the ‘History Buffer’ mitigation if desired. The default QAT driver configuration option sysctl dev.qat.X.disable_safe_dc_mode does not allow override of the mitigation. The new sysctl attribute disable_safe_dc_mode is to be set to 1 for overriding the history buffer mitigation. Firmware for qat_4xxx is updated for this change. If this mode is enabled, decompression throughput increases but may result in a data leak if num_user_processes is more than 1. This option is to be enabled only if your system is not prone to user data leaks. Reviewed by: markj, ziaee MFC after: 2 weeks Sponsored by: Intel Corporation Differential Revision: https://reviews.freebsd.org/D50379 (cherry picked from commit 5a8e5215cef0dac1115853889e925099f61bb5fa)
* mac_do(4): allow compiling into kernelLexi Winter2025-06-013-1/+4
| | | | | | | | | | The manual page says this is possible, but it's not. Make it possible. Reviewed by: olce, kevans Approved by: kevans (mentor) Differential Revision: https://reviews.freebsd.org/D50451 (cherry picked from commit c8d8cac2a8479009bcdca6c0cb9852af514896f2)
* mbuf: Allow clusters to fill an entire jumbo page.Dag-Erling Smørgrav2025-05-141-1/+2
| | | | | | | | | | | | | | | | The assumption that MCLBYTES == MJUMPAGESIZE can only happen if pages are small is incorrect: it can also happen if MCLSHIFT is adjusted to increase the size of clusters. Restore the ability to have clusters fill a jumbo page, while still disallowing them from exceeding them. MFC after: 1 week Fixes: 840327e5ddf3, 9c3ad5ba932b Sponsored by: NetApp, Inc. Sponsored by: Klara, Inc. Reviewed by: siderop1_netapp.com, kevans, brooks Differential Revision: https://reviews.freebsd.org/D50242 (cherry picked from commit 271128b0698653294acf0ed3457d5871af5b3ef1)
* arm: remove accidentally added -Map switch to linkerMichal Meloun2025-05-031-1/+0
| | | | | Fixes: ba045ba49ded (cherry picked from commit 0283eebb4a54c7270f9ac03bb4ed2742cb959c28)
* arm: Improve the creation of kernel.binMichal Meloun2025-05-032-19/+21
| | | | | | | | | | | | | | | | | | | Instead of relinking the kernel without elf headers, replace them with a binary blob of the same length starting with a jump to the kernel's start address. This ensures that all symbols stay at the same offsets as in the original kernel, so kernel.debug remains valid also for kernel.bin. Also ensure that the awk script used runs with the neutral locale defined. Awk 'write' is a locale compilant, and script is used to write binary data to a file, so it needs to ensure that bytes > 127 are written unchanged. While I'm on, set the neutral locale also for arm64, where the same script is used to generate the kernel booti image. Reviewed by: emaste, imp Differential Revision: https://reviews.freebsd.org/D47488 (cherry picked from commit ba045ba49dedb068ba2f0e13fbb1c1a91fde8333)
* Post-14.3-branch updatesColin Percival2025-05-021-1/+1
| | | | | | | | | Rename stable/14 to -STABLE Bump __FreeBSD_version Approved by: re (implicit) Sponsored by: Amazon
* mpi3mr: Broadcom's MPT-Fusion version 4 is amd64 and aarch64 onlyWarner Losh2025-04-301-1/+2
| | | | | | | | | | | | | | | Broadcom's MPT-Fusion version 4 driver only works on 64-bit systems, and has only been tested in amd64 and aarch64, so move it's building to just those. I didn't notice this in the review and neglected to test those cases (since I knew it didn't work there, so was a blind spot). Pointy-hat: imp Fixes: 9cdd40759617 Sponsored-by: Netflix Sponsored by: Netflix (cherry picked from commit 2f721943bf20e53b0ba7b5032a2900d0beb67413)
* mpi3mr: Allow driver to be in-kenrel and add to GENERICChandrakanth patil2025-04-302-0/+6
| | | | | | | | | | | | | | | | | | | | | | | Registered the mpi3mr driver source files in sys/conf/files, enabling it to be compiled into the base kernel image. This matches the approach used for existing Broadcom drivers such as mrsas, mps, and mpr. Add mpi3mr to sys/conf/NOTES. With this change, the mpi3mr driver will be built as part of the base kernel, allowing automatic loading during boot when supported hardware is detected. Below changes are suggested by chs@: - Corrected the file name typo mistake in /sys/conf/files from mpi3mr_app.c.c to mpi3mr_app.c - Added mpi3mr driver entries in "sys/amd64/conf/GENERIC" and "sys/i386/conf/GENERIC" Reviewed by: ssaxena, chs, imp Differential Revision: https://reviews.freebsd.org/D49754 (cherry picked from commit 9cdd40759617b15fdd6939d33f67aa2c9d2a6b1e)
* 14.3: Update stable/14 to -PRERELEASEColin Percival2025-04-191-2/+2
| | | | | | | | | | | | | This marks the start of the FreeBSD 14.3 release cycle; the stable/14 tree is now in "code slush". Developers are encouraged to prioritize fixing bugs (and/or merging bug fixes from HEAD) over new features at this time. Commit approval from re@ is not required but if new features introduce problems they may be removed from the release. Approved by: re (implicit) Sponsored by: Amazon
* zfs: enable FPU on powerpc*Piotr Kubaj2025-04-041-2/+11
| | | | | | Differential Revision: https://reviews.freebsd.org/D49538 (cherry picked from commit 5b02365ac656e1cccf293ec1c57a8eb6c5cd51e2)
* conf: Add acpi_pci.c to the arm64 buildAndrew Turner2025-04-011-0/+1
| | | | | | | | | Reviewed by: jhb, emaste, cperciva Relnotes: yes (Support PCIe hotplug on arm64) Sponsored by: Arm Ltd Differential Revision: https://reviews.freebsd.org/D48049 (cherry picked from commit 38cb1ba8637d08ce3f6b3c614f39698db153cd4d)
* kern.mk: Update SSP comment (not limited to GCC)Ed Maste2025-03-261-1/+1
| | | | | | Sponsored by: The FreeBSD Foundation (cherry picked from commit 222c850503d1cbd5293c04987181a74b9dbe3fcf)
* clock: Simplify subr_ticks and renameMark Johnston2025-02-141-1/+1
| | | | | | | | | | | | | | | - We can use builtin constants for the size of int and long to simplify definitions. - The file should have a .S prefix since we want to run it through the preprocessor, though apparently this happens anyway with .s... - Move ticks and ticksl from .data to .bss. Reported by: jrtc27 Reviewed by: jrtc27, kib, emaste Fixes: 6b82130e6c9a ("clock: Add a long ticks variable, ticksl") Differential Revision: https://reviews.freebsd.org/D48420 (cherry picked from commit b2b974f7ef4cddff251d0de69d8da13232b25e4d)
* clock: Add a long ticks variable, tickslMark Johnston2025-02-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | For compatibility with Linux, it's useful to have a tick counter of width sizeof(long), but our tick counter is an int. Currently the linuxkpi tries paper over this difference, but this cannot really be done reliably, so it's desirable to have a wider tick counter. This change introduces ticksl, keeping the existing ticks variable. Follow a suggestion from kib to avoid having to maintain two separate counters and to avoid converting existing code to use ticksl: change hardclock() to update ticksl instead of ticks, and then use assembler directives to make ticks and ticksl overlap such that loading ticks gives the bottom 32 bits. This makes it possible to use ticksl in the linuxkpi without having to convert any native code, and without making hardclock() more complicated or expensive. Then, the linuxkpi can be modified to use ticksl instead of ticks. Reviewed by: olce, kib, emaste MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D48383 (cherry picked from commit 6b82130e6c9add4a8892ca897df5a0ec04663ea2)
* ng_ubt(4): do not attach Realtek 87XX/88XX adaptors in bootloader mode.Vladimir Kondratyev2024-12-221-0/+1
| | | | | | | | | | | | | | | Attempt to initialize FreeBSD bluetooth stack while such a device is in bootloader mode locks the adapter hardly so it requires power on/off cycle to restore. This change blocks ng_ubt attachment unless operational firmware is loaded thus preventing the lock up. Sponsored by: Future Crew LLC MFC after: 1 month Differential Revision: https://reviews.freebsd.org/D46738 (cherry picked from commit 24ae172a50352ad4fd22989477f29ecca5aed6e3)
* newvers: Set explicit git revision lengthPat Maddox2024-12-161-1/+1
| | | | | | | | | | | The --short flag is configurable. Setting an explicit length supports reproducible builds. Signed-off-by: Pat Maddox <pat@patmaddox.com> Reviewed by: emaste, imp Differential Revision: https://github.com/freebsd/freebsd-src/pull/1547 (cherry picked from commit a1097094c4c5d810287aca092f4ab5f9f86a426a)
* zfs: merge openzfs/zfs@e269af1b3 (zfs-2.2-release) into stable/14Martin Matuska2024-12-121-1/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OpenZFS release 2.2.7 Notable upstream pull request merges: #15457 022bf8637 Increase L2ARC write rate and headroom #15527 1ba5b2ef8 freebsd: remove __FBSDID macro use #15792 9e7af55e8 Add custom debug printing for your asserts #15793 a1ea40af8 libzfs: use zfs_strerror() in place of strerror() #16181 -multiple zdb/ztest: improve and harmonise crash output #16208 e5e4957a5 Allow block cloning to be interrupted by a signal #16210 ba4e582a6 FreeBSD: Add const qualifier to members of struct opensolaris_utsname #16225 a6198f34b Simplify issig() #16335 25ec9a903 zdb: fix BRT dump #16364 cf80a803d zvol: ensure device minors are properly cleaned up #16404 384b53be8 FreeBSD: Add missing memory reclamation accounting #16492 -multiple Split "shared" userspace & kernel code into separate files #16496 f1694496a zfs_file: rename zfs_file_fallocate to zfs_file_deallocate #16511 bc0d89bfc Fix an uninitialized data access #16529 2dc8529d9 Fix handling of DNS names with '-' in them for sharenfs #16539 30ea44296 zfs_log: add flex array fields to log record structs #16546 098789216 Evicting too many bytes from MFU metadata #16551 54278533a Reduce and handle EAGAIN errors on AIO label reads #16554 84ad1d536 FreeBSD: restore zfs_znode_update_vfs() #16565 21c40e6d9 FreeBSD: Sync taskq_cancel_id() returns with Linux #16567 48482bb2f Properly release key in spa_keystore_dsl_key_hold_dd() #16584 e8f4592a1 Avoid computing strlen() inside loops #16605 acc8a3186 ARC: Cache arc_c value during arc_evict() #16650 fc60e0c6e freebsd: Use compiler.h from FreeBSD's base's linuxkpi #16667 b32b35cea zdb: show bp in uberblock dump #16684 1f5e1b919 Pack dmu_buf_impl_t by 16 bytes #16688 73b3e8ace Fix gcc uninitialized warning in FreeBSD zio_crypt.c #16690 727506c94 On the first vdev open ignore impossible ashift hints #16692 d83cd5307 zdb: add extra -T flag to show histograms of BRT refcounts #16693 82ab837a0 Fix gcc unused value warning in FreeBSD simd.h #16740 2bba6e3c5 BRT: Don't call brt_pending_remove() on holes/embedded #16801 299da6ace Fix race in libzfs_run_process_impl Obtained from: OpenZFS OpenZFS commit: e269af1b3c7b1b1c000d05f147a2f75e5e72e0ca OpenZFS tag: zfs-2.2.7
* arm: align data section to the supersection.Michal Meloun2024-12-081-3/+1
| | | | | | | | | Offset based data section alignment is probably not applicable to any system other than i386. MFC after: 4 week (cherry picked from commit 60e72eb16a08bdebb40c99cdfcde04e606fe4f3e)
* arm: add read_frequently, read_mostly and exclusive_cache_line sections to ↵Michal Meloun2024-12-081-0/+15
| | | | | | | | linker script. MFC after: 1 week (cherry picked from commit d98a18d032e6ed3dbae30233d217c6597000e391)
* arm: fix symbols around the .ARM.exidx sectionMichal Meloun2024-12-081-0/+1
| | | | | | | | | | | Insert a direct assignment to the location counter to ensure that orphaned sections cannot be emitted between the _exidx_start symbol and the .ARM.exidx section. Discussed with: jrtc27 MFC after: 1 week (cherry picked from commit 1701dfae1be3be6f8f1fdd3b6b636d3161b33420)
* arm: Fix typo in ldscript.arm.Michal Meloun2024-12-081-1/+1
| | | | | | MFC after: 1 week (cherry picked from commit 0381f0b63b9a5e55d4eca3da5c35ab55e4ce948b)
* sound: Merge ac97 and ac97_patchChristos Margiolis2024-12-041-1/+0
| | | | | | | | | | | No functional change intended. Sponsored by: The FreeBSD Foundation MFC after: 2 days Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D47732 (cherry picked from commit 0b4e32912566d802c7a6501d9ce8119f04dbc2fb)
* gve: Add DQO RDA supportShailend Chand2024-11-201-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | DQO is the descriptor format for our next generation virtual NIC. It is necessary to make full use of the hardware bandwidth on many newer GCP VM shapes. One major change with DQO from its predecessor GQI is that it uses dual descriptor rings for both TX and RX queues. The TX path uses a descriptor ring to send descriptors to HW, and receives packet completion events on a TX completion ring. The RX path posts buffers to HW using an RX descriptor ring and receives incoming packets on an RX completion ring. In GQI-QPL, the hardware could not access arbitrary regions of guest memory, which is why there was a pre-negotitated bounce buffer (QPL: Queue Page List). DQO-RDA has no such limitation. "RDA" is in contrast to QPL and stands for "Raw DMA Addressing" which just means that HW does not need a fixed bounce buffer and can DMA arbitrary regions of guest memory. A subsequent patch will introduce the DQO-QPL datapath that uses the same descriptor format as in this patch, but will have a fixed bounce buffer. Signed-off-by: Shailend Chand <shailend@google.com> Reviewed-by: markj MFC-after: 2 weeks Differential Revision: https://reviews.freebsd.org/D46690 (cherry picked from commit d438b4ef0cfc6986b93d0754f49ebf3ead50f269)
* AMD IOMMU driverKonstantin Belousov2024-11-091-0/+6
| | | | (cherry picked from commit 0f5116d7efe33c81f0b24b56eec78af37898f500)
generated by cgit v1.3 (git 2.53.0) at 2026-04-18 15:13:13 +0000