aboutsummaryrefslogtreecommitdiff
path: root/share/man/man4
Commit message (Collapse)AuthorAgeFilesLines
* vmgenc.4: Add VM Generation ID Counter manualChristos Longros41 hours2-0/+63
| | | | | | | | | | | | Document the vmgenc(4) ACPI driver which detects virtual machine cloning and snapshot restoration via the VM Generation ID specification. The driver reseeds the kernel entropy pool when a generation change is detected. MFC after: 3 days Reviewed by: cem (previous), ziaee Signed-off-by: Christos Longros <chris.longros@gmail.com> Differential Revision: https://reviews.freebsd.org/D56011
* pkgbase: Move all of ATF into the atf packageDag-Erling Smørgrav2 days1-5/+5
| | | | | | | | | | | | Parts of ATF (including the licence and some of the documentation) were for some reason part of the tests package instead of the atf package. Moving them to where they logically belong poses no problem since tests already depends on atf. PR: 294129 MFC after: 1 week Reviewed by: ivy Differential Revision: https://reviews.freebsd.org/D56158
* asmc(4): Bump manpage date after editionVladimir Kondratyev3 days1-1/+1
| | | | | Fixes: 5d7862fb998f ("asmc(4): Add support for backlight(9) interface") MFC after: 1 month
* asmc(4): Add support for backlight(9) interfaceVladimir Kondratyev3 days1-1/+10
| | | | MFC after: 1 month
* ufshci: add uic powermode parameter to sysctlJaeyoon Choi8 days1-1/+33
| | | | | | | | | Adds parameters related to the performance of the UFS device. Also update man page for the missing sysctl entries. Sponsored by: Samsung Electronics Reviewed by: imp (mentor) Differential Revision: https://reviews.freebsd.org/D55985
* rge: make rx_process_limit a sysctl tunableChristos Longros8 days1-0/+5
| | | | | | | | | | | The number of packets processed per interrupt was hardcoded to 16. Add a per-interface sysctl dev.rge.%d.rx_process_limit tunable so users can adjust this value at runtime. Signed-off-by: Christos Longros <chris.longros@gmail.com> Reviewed by: ziaee, adrian Differential Revision: https://reviews.freebsd.org/D56014
* rge.4: fix incorrect speed range in HARDWARE sectionChristos Longros8 days1-2/+17
| | | | | | | | | | | | | | | | | | | | The HARDWARE section stated "PCIe 1GB to 1GB Ethernet devices" which is incorrect. The RTL8125/8126/8127 chips support speeds from 1Gbps to 10Gbps. Correct the range. Signed-off-by: Christos Longros <chris.longros@gmail.com> rge.4: note that the driver manages PHY directly The rge(4) driver does not use the miibus(4) interface for PHY management. Instead, it accesses PHY registers directly via the chip's OCP (On-Chip Peripheral) bus. Document this in the DESCRIPTION section. Signed-off-by: Christos Longros <chris.longros@gmail.com> Reviewed by: adrian Differential Revision: https://reviews.freebsd.org/D55995
* hwpmc.4: correct stale default values and update diagnosticsPaulo Fragoso9 days1-6/+19
| | | | | | | | | | | | | | | | | The default values documented for kern.hwpmc.logbuffersize (4KB) and kern.hwpmc.nbuffers_pcpu (64) have been incorrect since 2981a3420cb1 (2018), which updated the compiled defaults but did not update the man page. - Correct logbuffersize default from 4KB to 256KB, add 16MB maximum - Correct nbuffers_pcpu default from 64 to 32, document 32MB per-CPU product limit with kern.hwpmc.logbuffersize - Update DIAGNOSTICS section to reflect current warning messages Reviewed by: mhorne MFC after: 1 week Sponsored by: NLINK (nlink.com.br) Differential Revision: https://reviews.freebsd.org/D56050
* acpi.4: Update sysctl descriptions for new stypesAymeric Wibo12 days1-13/+14
| | | | | | | | | | | | | The previous S1-S5 options are still accepted for compatibility, but they are now deprecated in favour of the new generic sleep types. Reported by: markj Reviewed by: markj Approved by: markj Fixes: 97d152698f48 ("acpi: Use sleep types defined in sys/power.h") Event: AsiaBSDCon 2026 Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D56008
* dwcotg.4: Initial manual pageAlexander Ziaee12 days2-0/+30
| | | | | | | | Create visibility in apropos and the Hardware Release Notes. MFC after: 3 days Reviewed by: pauamma, ray Differential Revision: https://reviews.freebsd.org/D53287
* libpmc: Query hwpmc for capsAli Mashtizadeh2026-03-161-0/+4
| | | | | | | | | | | | | This change allows for fine-grained capabilities per counter index. This is particularly useful for AMD where subclasses are not exposed to the general PMC code, but other architectures also have asymmetric behaviors when it comes to specific counter indices. A new PMC_OP_GETCAPS op is added to the hwpmc(4) ioctl interface. Reviewed by: mhorne Sponsored by: Netflix Pull Request: https://github.com/freebsd/freebsd-src/pull/2058
* re(4), rge(4): improve Realtek driver man pagesChristos Longros2026-03-142-0/+6
| | | | | | | | | | | | | Add D-Link DGE-530(T) and Killer E2600 to the re(4) HARDWARE list. Both are supported by the driver but were missing from the man page. Also add cross-references between re(4) and rge(4) in SEE ALSO, as both are Realtek NIC drivers. Signed-off-by: Christos Longros <chris.longros@gmail.com> Reviewed by: adrian Differential Revision: https://reviews.freebsd.org/D55745
* carp: retire ioctl(2) APIGleb Smirnoff2026-03-121-9/+3
| | | | | | | | | All supported stable branches use netlink(4) API to configure carp(4). The deleted code also has kernel stack leak vulnerability, that requires extra effort to fix. Reviewed by: pouria, kp Differential Revision: https://reviews.freebsd.org/D55804
* pci: Export bus numbers for bridge devices in struct pci_confJohn Baldwin2026-03-101-0/+6
| | | | | | | | | | | This exports bus information about bridges to userspace via the less-privileged PCIOCGETCONF ioctl. Previously if userspace wished to query this information, it had to use direct PCI config register access which requires higher privilege. Reviewed by: imp Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D55771
* pci.4: Quote argument to -width for a list blockJohn Baldwin2026-03-101-3/+3
| | | | | | | | | | | | This fixes an mdoc warning and also properly indents this list. While here, update the quoted argument to be the longest tag in the list. Also while here, correct the description of pd_numa_domain. NUMA domains are a property of the device, not of the driver. Reviewed by: ziaee, imp Sponsored by: Chelsio Communications Differential Revision: https://reviews.freebsd.org/D55770
* Fix typos in manual pagesChristos Longros2026-03-091-1/+1
| | | | | | | | | | bpf.4: accomodate -> accommodate hier.7: compatability -> compatibility namei.9: succesfull -> successful Signed-off-by: Christos Longros <chris.longros@gmail.com> Reviewed by: emaste Differential Revision: https://reviews.freebsd.org/D55746
* igc.4: Describe betterAlexander Ziaee2026-03-091-4/+4
| | | | MFC after: 3 days
* ndp: Add support for Gratuitous Neighbor Discovery (GRAND)Pouria Mousavizadeh Tehrani2026-03-051-1/+12
| | | | | | | | | | Implement RFC 4861 Section 7.2.6 and RFC 9131, which is also address one of the IPv6 deployment issues in RFC 9898 Section 3.9. GRAND should be triggered by a change in link-layer address of interface or by configuration of a new global ipv6 address after DAD completes. Reviewed by: glebius Differential Revision: https://reviews.freebsd.org/D55015
* ichwd: Add manual for i6300esb watchdogShengYi Hung2026-03-041-1/+11
| | | | | | | | Reviewed by: ziaee, mhorne Approved by: lwhsu (mentor) MFC after: 2 weeks Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D54466
* me.4: note that it is a point-to-point interfaceEugene Grosbein2026-03-041-2/+2
| | | | | | Add explicit note that me(4) works as a point-to-point pseudo device. MFC after: 1 week
* me.4: link if_me kernel module to its manual page.Eugene Grosbein2026-03-041-0/+1
| | | | MFC after: 1 week
* sys: Retire le(4)Ed Maste2026-03-022-376/+0
| | | | | | | | | | | | | | | | We retired most obsolete 10 and 10/100 Ethernet NIC drivers in 2019 -- see commits following ebcf740a32ae ("FCP-101: remove obsolete 10 and 10/100 Ethernet drivers.). le(4) was retained with with the note "Emulated by QEMU, alternatives don't yet work for mips64." MIPS has since been removed from the tree and emulators and virtual machines offer many other, more suitable devices. Reviewed by: brooks Relnotes: Yes Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D55516
* virtio: add loader tunables to sysctlTimo Völker2026-03-021-2/+26
| | | | | | | | | | virtio_pci uses two loader tunables that should be more visible. This patch adds these loader tunables to sysctl and describes them in the virtio(4) man page. Reviewed by: imp (erlier version), tuexen MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D55533
* rge.4: correct media types in the manual pageKevin Lo2026-02-261-8/+8
| | | | | | | Correct media types for 1000Mbit/s, 2500Mbit/s, 5000Mbit/s and 10Gbit/s. Reviewed by: adrian Differential Revision: https://reviews.freebsd.org/D55496
* ffs.4: Mlink to ufs.4Alexander Ziaee2026-02-242-2/+4
| | | | | | PR: 293423 MFC after: 3 days Requested by: bms
* vmm.4: Fix widthMark Johnston2026-02-191-1/+1
| | | | | Reported by: ziaee Fixes: d26c8ae527bb ("vmm.4: Add information on VM access control")
* vmm.4: Add information on VM access controlMark Johnston2026-02-191-0/+39
| | | | | | | | | Add a section to vmm.4 explaining how vmm device file ownership works. MFC after: 2 months Sponsored by: The FreeBSD Foundation Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D54742
* Correct Identifer typo in SPDX tagsEd Maste2026-02-182-2/+2
|
* multicast.4: Fix disabling multicast forwardingPouria Mousavizadeh Tehrani2026-02-131-4/+22
| | | | | | Reviewed by: markj, glebius MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D55266
* rtw88: remove more references to rtw88fwBjoern A. Zeeb2026-02-101-3/+2
| | | | | | | | | | When I removed the Realtek rtww8x firmware from base I missed to add rtw88fw.4 to ObsoleteFiles.inc [1]. While adding this, also remove a leftover reference in rtw88.4. Reported by: Herbert J. Skuhra (herbert gojira.at) [1] Fixes: cf94672363d6 MFC after: 3 days
* vt.4: Sprinkle mdoc macrosAlexander Ziaee2026-02-011-35/+35
| | | | | | | | | | Now that we have angle bracket characters for all common display sizes, sprinkle in the correct macros for the structures in this page. While here, fix a mdoc typo, a linter warning, and switch a parenthetical to a much smoother appositive. MFC after: 3 days Fixes: 7cd6da268a8f (vt.4: Style pass)
* INDEX.fonts: Minor maintenanceAlexander Ziaee2026-02-011-0/+3
| | | | | | | | + Mention relevance of this file in the vt manual screen.font entry + The vidfont manual is in section one, not eight + Remove leftover blank line from freebsd tag removal MFC after: 3 days
* epair: add VLAN_HWTAGGINGTimo Völker2026-01-301-1/+19
| | | | | | | | | | | | | | | | | | | | | | Add capability VLAN_HWTAGGING to the epair interface and enable it by default. When sending a packet over a VLAN interface that uses an epair interface, the flag M_VLANTAG and the ether_vtag (which contains the VLAN ID and/or PCP) are set in the mbuf to inform the hardware that the VLAN header has to be added. The sending epair end does not need to actually add a VLAN header. It can just pass the mbuf with this setting to the other epair end, which receives the packet. The receiving epair end can just pass the mbuf with this setting to the upper layer. Due to this setting, the upper layer believes that there was a VLAN header that has been removed by the interface. If the packet later leaves the host, the outgoing physical interface can add the VLAN header in hardware if it supports VLAN_HWTAGGING. If not, the implementation of Ethernet or bridge adds the VLAN header in software. Reviewed by: zlei, tuexen MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D52465
* divert: Update divert.4 to mention pfMark Johnston2026-01-271-13/+15
| | | | | | | | | | | | pf's divert-to action can be used to pass packets to a divert socket, but divert.4 didn't mention this, only referencing ipfw. Try to make the text a bit more general. Reviewed by: igoro, kp, glebius MFC after: 2 weeks Sponsored by: OPNsense Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D54848
* witness: Provide facility to print detailed lock treeJonathan T. Looney2026-01-261-3/+47
| | | | | | | | | | | | | | | | | | | | | | | | When witness(4) detects lock order reversals (LORs), it prints information about the stack trace which caused the LOR. If available, it can also print information about the first stack trace which established the other lock ordering. However, it only does this for "simple" LORs where the two locks in question were directly locked in the opposite order. When the lock order was established through a more complex pattern of intermediate locks, WITNESS only prints the stack trace where it detected the LOR. This commit provides new functionality to provide more verbose information about the lock chain(s) which established the lock ordering. The new functionality can be disabled by setting the debug.witness.trace sysctl/tunable to 1. The new functionality is also available through the debug.witness.badstacks sysctl, which has been modified to always show the more verbose information. Reviewed by: markj, glebius (previous version), kib (previous version) Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D54785 MFC after: 1 month
* acpi_spmc: Add system power management controller driverAymeric Wibo2026-01-261-1/+3
| | | | | | | | | | | | | | | | | | | Add SPMC (system power management controller) driver as acpi_spmc. This is the device which provides the LPI device D-state constraints and allows for OSPM to send S0ix/modern standby entry/exit notifications. This supports the original Intel DSM (https://uefi.org/sites/default/files/resources/Intel_ACPI_Low_Power_S0_Idle.pdf, untested), the AMD DSM (tested), and the Microsoft DSM (tested). Before entry, acpi_spmc_check_constraints is called to notify of any violated power constraints. This will use acpi_pwr_get_state to get current device D-states when that gets added back. Reviewed by: olce Tested by: jkim, Oleksandr Kryvulia, Matthias Lanter Approved by: olce Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D48387
* rights.4: document CAP_PDWAITKonstantin Belousov2026-01-251-0/+3
| | | | | | | Noted by: markj Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D54592
* vt.4: Document that hw.vga.textmode does not apply for UEFI(8) bootMichael Osipov2026-01-241-1/+5
| | | | | | | PR: 292598 Approved by: ziaee, imp MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D54842
* capsicum.4: Replace 'fi' ligature and smart quotation markArtem Bunichev2026-01-231-5/+5
| | | | | | | | | While here, wrap the line to 80 characters. Reviewed by: jlduran Fixes: c54534e60263 ("capsicum.4: Add some more detail from the Capsicum paper") MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D54761
* mac(4): also list jails in the example enumeration of objectsKyle Evans2026-01-201-2/+2
| | | | | | | | | | | The prison may also be considered part of the subject by way of its ucred association, but I don't think this is significantly different enough today than before recent work -- policies could have always taken them into account, and some did (e.g., mac_bsdextended). Reported by: olce Reviewed by: olce, ziaee Differential Revision: https://reviews.freebsd.org/D54748
* netlink(4): Add snl(3) to See Also sectionPouria Mousavizadeh Tehrani2026-01-183-2/+7
| | | | | | | | While here, fix manlint warnings in rtnetlink(4). Reviewed by: melifaro, ziaee, glebius Approved by: glebius (mentor) Differential Revision: https://reviews.freebsd.org/D53786
* termios.4: Cross-reference stack(9) for STATUSArtem Bunichev2026-01-161-2/+4
| | | | | | | | | If the kernel is built without stack(9) (options STACK), then the mentioned sysctl(8) kern.tty_info_kstacks will not be found. MFC after: 3 days Reviewed by: kib, ziaee Differential Revision: https://reviews.freebsd.org/D54701
* bge: disable TXCSUM if UDP transmit checksum offloading is disabledMichael Tuexen2026-01-161-1/+9
| | | | | | | | | | | | | | | | | | | | The bge interface is special with respect to transmit checksumi offloading. In the default settings, an bge interface announces TXCSUM capabilities, but only supports TCP/IPv4 and not UDP/IPv4 due to limitations of some of the NICs. This results in problems when the bge interface becomes a member of a bridge. Since currently only the TXCSUM capabilities are synced when a member is added to a bridge and not the protocol specific capabilities, this can result in a situation where UDP packets are sent out using a bge interface without having a correct checksum. To mitigate this problem, initially don't announce TXCSUM capabilities, when UDP transmit checksum is disabled. It is still possible to enable TXCSUM capabilities via ifconfig. PR: 291420 Reviewed by: Timo Voelker MFC after: 3 days Differential Revision: https://reviews.freebsd.org/D54486
* jail: document the mac.label parameterKyle Evans2026-01-161-1/+3
| | | | | | | | | | In particular, we should provide a hint about mac.conf(5), since libjail will just use the mac_prepare_type(3) API to provide a reasonably sane interface for system administrators. Progammers wanting to fetch an arbitrary MAC label would need to bypass libjail and use jail_get(2) directly with their own prepared `struct mac`. Differential Revision: https://reviews.freebsd.org/D54067
* kern: mac: add various jail MAC hooksKyle Evans2026-01-161-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds the following hooks: - mpo_prison_check_attach: check for subject capability to attach to a given jail - mpo_prison_check_create: check for subject capability to create a jail with the given option set - mpo_prison_check_get: check for subject capability to fetch the given parameters for a jail - mpo_prison_check_set: check for subject capability to set the given parameters for a jail - mpo_prison_check_remove: check for subject capability to remove the jail check_get wouldn't typically be a privileged operation, but is included to give MAC policies a wider range of capabilities at a relatively low cost. We also add two more for the purpose of label propagation: - mpo_prison_created: surface the creation of a jail so that one can do propagation to, e.g., the root vnode or any mounts - mpo_prison_attached: attach an existing process to the jail so that one can propagate the jail label to the process, as appropriate. It is unclear if this is preferred vs. having separate associate entry points for each type of object we might associate. That would split these up like so: - prison_created -> prison_associate_vnode - prison_attached -> prison_associate_proc Some sample policy ideas that should be feasible to implement with this set of hooks, in case it's inspiring: - mac_bomb: policy that allows a poudriere user to construct jails without root privilege, given a restricted set of jail parameters. Slap a warning label on it. - mac_capsule: policy that realizes the capsule idea that I pitched[0] on -jail@ to create jails that are effectively immutable once sealed, using these hooks and a label. Perhaps a silly idea, but a downstream could consider a scenario where it can implement special jail enumeration using a MAC policy and a cooperating application that specifies non-parameter options to filter the results. [0] https://lists.freebsd.org/archives/freebsd-jail/2025-September/000550.html Reviewed by: olce (slightly earlier version) Differential Revision: https://reviews.freebsd.org/D53954
* mca(4): Add man pageJonathan T. Looney2026-01-142-0/+279
| | | | | | Reviewed by: markj Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D54115
* nvme: Add APST payload overridingAlexey Sukhoguzov2026-01-091-0/+12
| | | | | | | | | | | The apst_data tunable allows APST configuration to be adjusted during controller initialization. It accepts an array of encoded integers, each defining specific transition parameters. Relnotes: YES Signed-off-by: Alexey Sukhoguzov <sap@eseipi.net> Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1444
* nvme: Support Autonomous Power State Transition (APST)Alexey Sukhoguzov2026-01-091-0/+9
| | | | | | | | | | | APST is an optional NVMe power-saving feature that allows devices to autonomously enter higher non-operational power states after a certain amount of idle time, reducing the controller's overall power consumption. Signed-off-by: Alexey Sukhoguzov <sap@eseipi.net> Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1444
* smartpqi: update to version 4660.0.2002John Hall2026-01-091-3/+83
| | | | | | | | | | | | This updates the smartpqi driver to Microchip's latest available public release. Reviewed by: imp Approved by: imp Sponsored by: Microchip Technology Inc. Differential Revision: https://reviews.freebsd.org/D52507
* cam: Add probes for xpt actionsWarner Losh2026-01-082-0/+43
| | | | | | | | | | | | | | cam::xpt:action(union ccb *) cam::xpt:done((union ccb *) cam::xpt:async-cb(void *cbarg, uint32_t async_code, struct cam_path *path, void *async_arg); Called when xpt_action(), xpt_done*() and the xpt async callbacks are called. Sponsored by: Netflix Reviewed by: adrian Differential Revision: https://reviews.freebsd.org/D54469