17 files changed, 1442 insertions, 0 deletions

diff --git a/static/openbsd/man4/man4.amd64/Makefile b/static/openbsd/man4/man4.amd64/Makefile
new file mode 100644
index 00000000..ab1441b6
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/Makefile
@@ -0,0 +1,19 @@
+MAN = amdpcib.4 \
+      apm.4 \
+      autoconf.4 \
+      bios.4 \
+      cpu.4 \
+      efifb.4 \
+      intro.4 \
+      ioapic.4 \
+      mem.4 \
+      mpbios.4 \
+      mtrr.4 \
+      nvram.4 \
+      pctr.4 \
+      skgpio.4 \
+      tcpcib.4 \
+      vmm.4
+
+include ../../../mandoc.mk
+
diff --git a/static/openbsd/man4/man4.amd64/amdpcib.4 b/static/openbsd/man4/man4.amd64/amdpcib.4
new file mode 100644
index 00000000..16fe36c3
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/amdpcib.4
@@ -0,0 +1,33 @@
+.\"     $OpenBSD: amdpcib.4,v 1.3 2015/01/15 20:37:36 schwarze Exp $
+.\"
+.\" Marc Balmer, 2007. Public Domain.
+.\"
+.Dd $Mdocdate: January 15 2015 $
+.Dt AMDPCIB 4 amd64
+.Os
+.Sh NAME
+.Nm amdpcib
+.Nd AMD-8111 series LPC bridge and timecounter
+.Sh SYNOPSIS
+.Cd "amdpcib* at pci?"
+.Cd "isa* at amdpcib?"
+.Sh DESCRIPTION
+The
+.Nm
+driver provides support for the AMD-8111 LPC bridge and implements a
+32/64-bit 14.3 MHz (or variable) timecounter using the HPET timer.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr isa 4 ,
+.Xr pci 4 ,
+.Xr watchdog 4
+.Sh HISTORY
+The
+.Nm
+driver first appeared in
+.Ox 4.3 .
+.Sh AUTHORS
+The
+.Nm
+driver was written by
+.An Michael Shalayeff .
diff --git a/static/openbsd/man4/man4.amd64/apm.4 b/static/openbsd/man4/man4.amd64/apm.4
new file mode 100644
index 00000000..8ace7400
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/apm.4
@@ -0,0 +1,167 @@
+.\"	$OpenBSD: apm.4,v 1.10 2023/01/30 14:43:29 jcs Exp $
+.\"
+.\"	Copyright (c) 1998 Marco S. Hyman
+.\"
+.\"	Permission to copy all or part of this material for any purpose is
+.\"	granted provided that the above copyright notice and this paragraph
+.\"	are duplicated in all copies.  THIS SOFTWARE IS PROVIDED ``AS IS''
+.\"	AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT
+.\"	LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS
+.\"	FOR A PARTICULAR PURPOSE.
+.\"
+.Dd $Mdocdate: January 30 2023 $
+.Dt APM 4 amd64
+.Os
+.Sh NAME
+.Nm apm
+.Nd power management interface
+.Sh SYNOPSIS
+.Cd "acpi0 at mainbus?"
+.Sh DESCRIPTION
+The
+.Nm
+driver provides a user interface to the
+.Xr acpi 4
+driver.
+.Pp
+The
+.Nm
+driver implements the following
+.Xr ioctl 2
+calls.
+They are defined in
+.In machine/apmvar.h .
+.Bl -tag -width Ds
+.It Dv APM_IOC_REJECT
+.Em Not implemented . DO NOT USE .
+.It Dv APM_IOC_STANDBY
+.Pq Li "no parameters"
+Request
+.Dq standby
+mode.
+.It Dv APM_IOC_SUSPEND
+.Pq Li "no parameters"
+Request
+.Dq suspend
+mode.
+.It Dv APM_IOC_HIBERNATE
+.Pq Li "no parameters"
+Request
+.Dq hibernate
+mode.
+.It Dv APM_IOC_GETPOWER
+.Pq Li "struct apm_power_info"
+Request the current power state.
+The argument structure is as follows:
+.Bd -literal -offset indent
+struct apm_power_info {
+	u_char battery_state;
+	u_char ac_state;
+	u_char battery_life;
+	u_char spare1;
+	u_int minutes_left;
+	u_int spare2[6];
+};
+.Ed
+.Pp
+The following values are defined for
+.Va battery_state :
+.Bl -tag -width Ds
+.It Dv APM_BATT_HIGH
+Battery has a high state of charge.
+.It Dv APM_BATT_LOW
+Battery has a low state of charge.
+.It Dv APM_BATT_CRITICAL
+Battery has a critical state of charge.
+.It Dv APM_BATT_CHARGING
+Battery is not high, low, or critical and is currently charging.
+.It Dv APM_BATT_UNKNOWN
+Cannot read the current battery state.
+.It Dv APM_BATTERY_ABSENT
+No battery installed.
+.El
+.Pp
+The following values are defined for
+.Va ac_state :
+.Bl -tag -width Ds
+.It Dv APM_AC_OFF
+External power not detected.
+.It Dv APM_AC_ON
+External power detected.
+.It Dv APM_AC_BACKUP
+Backup power in use.
+.It Dv APM_AC_UNKNOWN
+External power state unknown.
+.El
+.Pp
+The
+.Va battery_life
+value contains the estimated percentage of battery life available.
+100% indicates a full charge.
+.Pp
+The
+.Va minutes_left
+value contains the estimated number of minutes of battery life
+remaining.
+.It Dv APM_IOC_DEV_CTL
+.Pq Li "struct apm_ctl"
+Allows an application to directly set the
+APM operating mode.
+The argument structure is as follows:
+.Bd -literal -offset indent
+struct apm_ctl {
+	u_int dev;
+	u_int mode;
+};
+.Ed
+.Pp
+.Va dev
+indicates the device, typically
+.Dv APM_DEV_ALLDEVS .
+.Pp
+.Va mode
+indicates the desired operating mode.
+Possible values are
+.Bl -tag -width Ds -compact -offset indent
+.It Dv APM_SYS_READY
+.It Dv APM_SYS_STANDBY
+.It Dv APM_SYS_SUSPEND
+.It Dv APM_SYS_OFF
+.It Dv APM_LASTREQ_INPROG
+.It Dv APM_LASTREQ_REJECTED
+.El
+.It Dv APM_IOC_PRN_CTL
+.Pq Li "int"
+This
+.Xr ioctl 2
+controls message output by the APM
+driver when a power change event is detected.
+The integer parameter is one of:
+.Bl -tag -width Ds
+.It Dv APM_PRINT_ON
+All power change events result in a message.
+This is the normal operating mode for the driver.
+.It Dv APM_PRINT_OFF
+Power change event messages are suppressed.
+.It Dv APM_PRINT_PCT
+Power change event messages are suppressed unless the estimated
+battery life percentage changes.
+.El
+.El
+.Sh FILES
+.Bl -tag -width "/dev/apmctlXXX"
+.It /dev/apm
+Power management data device.
+May only be opened read-only.
+May be opened by multiple concurrent users.
+.It /dev/apmctl
+Power management control device.
+May be opened read-write or write-only.
+May only be opened by one user at a time.
+An attempt to open the file when in use will fail, returning
+.Er EBUSY .
+.El
+.Sh SEE ALSO
+.Xr acpi 4 ,
+.Xr intro 4 ,
+.Xr halt 8
diff --git a/static/openbsd/man4/man4.amd64/autoconf.4 b/static/openbsd/man4/man4.amd64/autoconf.4
new file mode 100644
index 00000000..7a3b6888
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/autoconf.4
@@ -0,0 +1,52 @@
+.\"	$OpenBSD: autoconf.4,v 1.3 2007/05/31 19:19:53 jmc Exp $
+.\"
+.\" Copyright (c) 1994 Christopher G. Demetriou
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"      This product includes software developed by Christopher G. Demetriou.
+.\" 3. The name of the author may not be used to endorse or promote products
+.\"    derived from this software without specific prior written permission
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd $Mdocdate: May 31 2007 $
+.Dt AUTOCONF 4 amd64
+.Os
+.Sh NAME
+.Nm autoconf
+.Nd diagnostics from the autoconfiguration code
+.Sh DESCRIPTION
+When
+.Ox
+bootstraps it probes the innards of the machine
+on which it is running
+and locates controllers, drives, and other devices, printing out
+what it finds on the console.
+This procedure is driven by a system configuration table which is processed by
+.Xr config 8
+and compiled into each kernel.
+Devices which exist in the machine but are not configured into the
+kernel are usually not detected.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr boot_amd64 8 ,
+.Xr config 8
diff --git a/static/openbsd/man4/man4.amd64/bios.4 b/static/openbsd/man4/man4.amd64/bios.4
new file mode 100644
index 00000000..59e70b7e
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/bios.4
@@ -0,0 +1,51 @@
+.\"	$OpenBSD: bios.4,v 1.2 2007/05/31 19:19:53 jmc Exp $
+.\"
+.\" Copyright (c) 2001 Michael Shalayeff
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF MIND,
+.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd $Mdocdate: May 31 2007 $
+.Dt BIOS 4 amd64
+.Os
+.Sh NAME
+.Nm bios
+.Nd a driver for PC Firmware, aka BIOS
+.Sh SYNOPSIS
+.Cd "bios0 at mainbus0"
+.Sh DESCRIPTION
+.Ox
+provides support for a limited subset of PC firmware (aka BIOS) subsystems
+on this platform.
+Only SMBIOS is supported.
+.Pp
+SMBIOS provides detail about system hardware configuration
+and is used to attach
+.Xr ipmi 4
+on most systems.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr ipmi 4
+.Sh HISTORY
+The
+.Nm
+driver was introduced to this platform in
+.Ox 4.0 .
diff --git a/static/openbsd/man4/man4.amd64/cpu.4 b/static/openbsd/man4/man4.amd64/cpu.4
new file mode 100644
index 00000000..bd480c13
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/cpu.4
@@ -0,0 +1,78 @@
+.\"	$OpenBSD: cpu.4,v 1.10 2024/09/10 17:01:09 tb Exp $
+.\"
+.\" Copyright (c) 2004 Ted Unangst
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd $Mdocdate: September 10 2024 $
+.Dt CPU 4 amd64
+.Os
+.Sh NAME
+.Nm cpu
+.Nd Central Processing Unit
+.Sh SYNOPSIS
+.Cd "cpu0 at mainbus?"
+.Cd "cpu* at mainbus?"
+.Sh DESCRIPTION
+Several processor models have additional features that extend their base
+functionality, such as power and frequency control or thermal monitoring.
+.Pp
+The
+.Xr sysctl 2
+.Va hw.cpuspeed
+returns the current operating frequency of the processor,
+though on some processors this value may be only an approximation.
+If possible, speed may be adjusted by altering
+.Va hw.setperf
+from 0 to 100,
+representing percentage of maximum speed.
+.Pp
+There are several possible implementations for speed adjustment,
+all transparent to the user:
+.Bl -tag -width tenletters
+.It EST
+Enhanced SpeedStep found on Intel and VIA processors,
+offering frequency scaling with numerous positions.
+.It PowerNow
+Found on various AMD processors.
+It currently only supports a limited set of models in the K8 families.
+.El
+.Pp
+The presence of extended instruction sets can be determined by the sysctl
+.Va machdep :
+.Bl -tag -width "tenletters"
+.It xcrypt
+Supports the VIA AES encryption instruction set.
+.El
+.Pp
+The sysctl
+.Va hw.sensors
+returns the current temperature reported by the processor.
+.Sh SEE ALSO
+.Xr sysctl 8
+.Sh BUGS
+Due to the way in which thermal information is reported on Intel processors,
+the temperature may be off by exactly +/-15 degrees C.
+.Pp
+For multiprocessor kernels with more than one CPU sensor,
+processors report identical temperatures
+since the temperature is taken from the processor running the sensors update.
diff --git a/static/openbsd/man4/man4.amd64/efifb.4 b/static/openbsd/man4/man4.amd64/efifb.4
new file mode 100644
index 00000000..b1512ba8
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/efifb.4
@@ -0,0 +1,47 @@
+.\"	$OpenBSD: efifb.4,v 1.2 2015/08/31 15:28:39 jmc Exp $
+.\"
+.\" Copyright (c) 2015 YASUOKA Masahiko <yasuoka@yasuoka.net>
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.\" The following requests are required for all man pages.
+.\"
+.Dd $Mdocdate: August 31 2015 $
+.Dt EFIFB 4 amd64
+.Os
+.Sh NAME
+.Nm efifb
+.Nd EFI frame buffer
+.Sh SYNOPSIS
+.Cd "efifb* at mainbus?"
+.Cd "wsdisplay* at efifb?"
+.Sh DESCRIPTION
+The
+.Nm
+driver supports the frame buffer passed from UEFI,
+the Unified Extensible Firmware Interface.
+.Pp
+The
+.Nm
+driver interfaces the frame buffer with the
+.Xr wscons 4
+console framework.
+It does not provide direct device driver entry points
+but makes its functions available via the internal
+.Xr wsdisplay 4
+interface.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr mainbus 4 ,
+.Xr wscons 4 ,
+.Xr wsdisplay 4
diff --git a/static/openbsd/man4/man4.amd64/intro.4 b/static/openbsd/man4/man4.amd64/intro.4
new file mode 100644
index 00000000..9e35f84d
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/intro.4
@@ -0,0 +1,122 @@
+.\"	$OpenBSD: intro.4,v 1.40 2023/05/03 22:03:17 jmc Exp $
+.\"
+.\" Copyright (c) 1983, 1986, 1991 Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.Dd $Mdocdate: May 3 2023 $
+.Dt INTRO 4 amd64
+.Os
+.Sh NAME
+.Nm intro
+.Nd introduction to special files and hardware support
+.Sh DESCRIPTION
+The manual pages in section 4 describe the special files,
+related driver functions, and networking support
+available in the system.
+In this part of the manual, the SYNOPSIS section of
+each configurable device gives a sample specification
+for use in constructing a system description for the
+.Xr config 8
+program.
+The DIAGNOSTICS section lists messages which may appear on the console
+and/or in the system error log
+.Pa /var/log/messages
+due to errors in device operation;
+see
+.Xr syslogd 8
+for more information.
+.Pp
+This section contains both devices
+which may be configured into the system
+and network related information.
+The networking support is introduced in
+.Xr netintro 4 .
+.Sh DEVICE SUPPORT
+This section describes the hardware supported on the amd64 platform.
+Software support for these devices comes in two forms.
+A hardware device may be supported with a character or block
+.Em device driver ,
+or it may be used within the networking subsystem and have a
+.Em network interface driver .
+Block and character devices are accessed through files in the file
+system of a special type; see
+.Xr mknod 8 .
+Network interfaces are indirectly accessed through the interprocess
+communication facilities provided by the system; see
+.Xr socket 2 .
+.Pp
+A hardware device is identified to the system at configuration time
+and the appropriate device or network interface driver is then compiled
+into the system.
+When the resultant system is booted, the autoconfiguration facilities
+in the system probe for the device and, if found, enable the software
+support for it.
+If a device does not respond at autoconfiguration
+time, it is not accessible at any time afterwards.
+To enable a device which did not autoconfigure,
+the system will have to be rebooted.
+.Pp
+The autoconfiguration system is described in
+.Xr autoconf 4 .
+.Sh LIST OF DEVICES
+A complete list of available devices is contained within the pages
+describing the system buses and controllers.
+For example, a PCI device would be listed in the
+.Xr pci 4
+man page.
+The following buses and controllers list these devices:
+.Pp
+.Bl -tag -width "cardbus(4)XX" -offset 3n -compact
+.It Xr acpi 4
+Advanced Configuration and Power Interface
+.It Xr cardbus 4
+introduction to CardBus support
+.It Xr iic 4
+Inter IC (I2C) bus
+.It Xr isa 4
+introduction to ISA bus support
+.It Xr onewire 4
+1-Wire bus
+.It Xr pci 4
+introduction to PCI bus support
+.It Xr pcmcia 4
+introduction to PCMCIA (PC Card) support
+.It Xr usb 4
+introduction to Universal Serial Bus support
+.It Xr virtio 4
+VirtIO support driver
+.El
+.Sh SEE ALSO
+.Xr autoconf 4 ,
+.Xr cpu 4 ,
+.Xr config 8
+.Sh HISTORY
+The
+amd64
+.Nm intro
+first appeared in
+.Ox 3.5 .
diff --git a/static/openbsd/man4/man4.amd64/ioapic.4 b/static/openbsd/man4/man4.amd64/ioapic.4
new file mode 100644
index 00000000..01dccda9
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/ioapic.4
@@ -0,0 +1,46 @@
+.\"   $OpenBSD: ioapic.4,v 1.3 2007/05/31 19:19:53 jmc Exp $
+.\"
+.\" Copyright (c) 2006 Mark Kettenis
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.Dd $Mdocdate: May 31 2007 $
+.Dt IOAPIC 4 amd64
+.Os
+.Sh NAME
+.Nm ioapic
+.Nd I/O Advanced Programmable Interrupt Controller
+.Sh SYNOPSIS
+.Cd "ioapic0 at mainbus0"
+.Sh DESCRIPTION
+.Nm
+is an I/O Advanced Programmable Interrupt Controller (APIC).
+It provides interrupt management for systems with multiple I/O
+subsystems and can distribute interrupts across multiple processors.
+.Sh SEE ALSO
+.Xr intro 4
+.Sh STANDARDS
+.Nm
+is based on
+Intel's 82093AA I/O Advanced Programmable Interrupt Controller (I/O APIC)
+specification.
+.Sh HISTORY
+The
+.Nm
+driver first appeared in
+.Ox 3.5 .
+.Sh AUTHORS
+The
+.Nm
+driver was written by
+.An Bill Sommerfield .
diff --git a/static/openbsd/man4/man4.amd64/mem.4 b/static/openbsd/man4/man4.amd64/mem.4
new file mode 100644
index 00000000..64135758
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/mem.4
@@ -0,0 +1,87 @@
+.\"	$OpenBSD: mem.4,v 1.7 2024/03/22 12:29:33 jsg Exp $
+.\"
+.\" Copyright (c) 1991 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"	from: @(#)mem.4	5.3 (Berkeley) 5/2/91
+.\"
+.Dd $Mdocdate: March 22 2024 $
+.Dt MEM 4 amd64
+.Os
+.Sh NAME
+.Nm mem ,
+.Nm kmem
+.Nd memory files
+.Sh DESCRIPTION
+The special file
+.Pa /dev/mem
+is an interface to the physical memory of the computer.
+Byte offsets in this file are interpreted as physical memory addresses.
+Reading and writing this file is equivalent to reading and writing
+memory itself.
+Only offsets within the bounds of
+.Pa /dev/mem
+are allowed.
+.Pp
+Kernel virtual memory is accessed through the interface
+.Pa /dev/kmem
+in the same manner as
+.Pa /dev/mem .
+Only kernel virtual addresses that are currently mapped to memory are allowed.
+.Pp
+On amd64, physical memory is discontiguous; especially,
+the ISA I/O memory space covers the physical address range from
+.Li 0x000a0000
+to
+.Li 0x00100000 .
+.Pp
+The kernel virtual memory begins at address
+.Li 0xffffffff80000000 .
+.Pp
+Even with sufficient file system permissions,
+these devices can only be opened when the
+.Xr securelevel 7
+is insecure or when the
+.Va kern.allowkmem
+.Xr sysctl 2
+variable is set.
+.Sh FILES
+.Bl -tag -width Pa -compact
+.It Pa /dev/mem
+.It Pa /dev/kmem
+.El
+.Sh SEE ALSO
+.Xr mtrr 4 ,
+.Xr securelevel 7
+.Sh HISTORY
+The
+.Pa /dev/mem
+file appeared in
+.At v1 ,
+.Pa /dev/kmem
+appeared in
+.At v5 .
diff --git a/static/openbsd/man4/man4.amd64/mpbios.4 b/static/openbsd/man4/man4.amd64/mpbios.4
new file mode 100644
index 00000000..69a9136f
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/mpbios.4
@@ -0,0 +1,58 @@
+.\"     $OpenBSD: mpbios.4,v 1.1 2009/01/13 13:57:03 kettenis Exp $
+.\"
+.\" Copyright (c) 2009 Mark Kettenis <kettenis@openbsd.org>
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.Dd $Mdocdate: January 13 2009 $
+.Dt MPBIOS 4 amd64
+.Os
+.Sh NAME
+.Nm mpbios
+.Nd MP BIOS
+.Sh SYNOPSIS
+.Cd "mpbios0 at bios0"
+.Sh DESCRIPTION
+The
+.Nm
+driver extracts configuration information from the BIOS on
+multiprocessor systems that conform to the Intel MultiProcessor
+Specification.
+This information is used to attach application processors and APICs,
+and to assign interrupts to ISA, EISA and PCI devices.
+.Pp
+On modern systems this information is provided by ACPI through the
+.Xr acpimadt 4
+device.
+On such a system
+.Nm
+will not attach, even if the BIOS also contains the data structures
+specified by the Intel MP Specification.
+.Pp
+The
+.Nm
+driver supports version 1.1 and 1.4 of the Intel MP Specification.
+.Sh SEE ALSO
+.Xr acpi 4 ,
+.Xr acpimadt 4 ,
+.Xr bios 4 ,
+.Xr cpu 4 ,
+.Xr intro 4 ,
+.Xr ioapic 4
+.Sh HISTORY
+The
+.Nm
+driver first appeared in
+.Ox 4.5 ,
+based on code present since
+.Ox 3.6 .
diff --git a/static/openbsd/man4/man4.amd64/mtrr.4 b/static/openbsd/man4/man4.amd64/mtrr.4
new file mode 100644
index 00000000..4a88f4ac
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/mtrr.4
@@ -0,0 +1,146 @@
+.\"	$OpenBSD: mtrr.4,v 1.8 2014/02/15 23:41:19 schwarze Exp $
+.\"
+.\" MTRR driver for OpenBSD.
+.\" Copyright 1999 Matthieu Herrb <matthieu@openbsd.org>
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.Dd $Mdocdate: February 15 2014 $
+.Dt MTRR 4 amd64
+.Os
+.Sh NAME
+.Nm mtrr
+.Nd driver for CPU memory range attributes
+.Sh SYNOPSIS
+.Cd "pseudo-device mtrr 1"
+.Sh DESCRIPTION
+The
+.Nm
+device provides access to the memory range attributes supported by the
+MTRRs on AMD64 compatible CPUs.
+.Ss IOCTL INTERFACE
+Several architectures allow attributes to be associated with ranges of physical
+memory.
+These attributes can be manipulated via
+.Fn ioctl
+calls performed on
+.Pa /dev/mem
+or
+.Pa /dev/xf86 .
+Declarations and data types are to be found in
+.In sys/memrange.h .
+.Pp
+The specific attributes, and number of programmable ranges may vary between
+architectures.
+The full set of supported attributes is:
+.Bl -tag -width MDF_WRITECOMBINE
+.It Dv MDF_UNCACHEABLE
+The region is not cached.
+.It Dv MDF_WRITECOMBINE
+Writes to the region may be combined or performed out of order.
+.It Dv MDF_WRITETHROUGH
+Writes to the region are committed synchronously.
+.It Dv MDF_WRITEBACK
+Writes to the region are committed asynchronously.
+.It Dv MDF_WRITEPROTECT
+The region cannot be written to.
+.El
+.Pp
+Memory ranges are described by
+.Bd -literal -offset xxxx
+struct mem_range_desc {
+	u_int64_t	mr_base;	/\(** physical base address \(**/
+	u_int64_t	mr_len;		/\(** physical length of region \(**/
+	int		mr_flags;	/\(** attributes of region \(**/
+	char		mr_owner[8];
+};
+.Ed
+.Pp
+In addition to the region attributes listed above, the following flags
+may also be set in the
+.Fa mr_flags
+field:
+.Bl -tag -width MDF_FIXACTIVE
+.It Dv MDF_FIXBASE
+The region's base address cannot be changed.
+.It Dv MDF_FIXLEN
+The region's length cannot be changed.
+.It Dv MDF_FIRMWARE
+The region is believed to have been established by the system firmware.
+.It Dv MDF_ACTIVE
+The region is currently active.
+.It Dv MDF_BOGUS
+We believe the region to be invalid or otherwise erroneous.
+.It Dv MDF_FIXACTIVE
+The region cannot be disabled.
+.El
+.Pp
+Operations are performed using
+.Bd -literal -offset xxxx
+struct mem_range_op {
+	struct mem_range_desc	*mo_desc;
+	int			mo_arg[2];
+};
+.Ed
+.Pp
+The
+.Fa MEMRANGE_GET
+ioctl is used to retrieve current memory range attributes.
+If
+.Fa mo_arg[0]
+is set to 0, it will be updated with the total number of memory range
+descriptors.
+If greater than 0, the array at
+.Fa mo_desc
+will be filled with a corresponding number of descriptor structures,
+or the maximum, whichever is less.
+.Pp
+The
+.Fa MEMRANGE_SET
+ioctl is used to add, alter and remove memory range attributes.
+A range with the
+.Dv MDF_FIXACTIVE
+flag may not be removed.
+.Pp
+.Fa mo_arg[0]
+should be set to MEMRANGE_SET_UPDATE to update an existing
+or establish a new range, or to MEMRANGE_SET_REMOVE to remove a range.
+.Sh ERRORS
+On
+.Xr ioctl 2
+failure,
+.Xr errno 2
+will be set as follows:
+.Bl -tag -width Er
+.It Bq Er EOPNOTSUPP
+Memory range operations are not supported on this architecture.
+.It Bq Er ENXIO
+No memory range descriptors are available (e.g., firmware has not enabled
+any).
+.It Bq Er EINVAL
+The memory range supplied as an argument is invalid or overlaps another
+range in a fashion not supported by this architecture.
+.It Bq Er EBUSY
+An attempt to remove or update a range failed because the range is busy.
+.It Bq Er ENOSPC
+An attempt to create a new range failed due to a shortage of hardware
+resources (e.g., descriptor slots).
+.It Bq Er ENOENT
+An attempt to remove a range failed because no range matches the descriptor
+base/length supplied.
+.It Bq Er EPERM
+An attempt to remove a range failed because the range is permanently
+enabled.
+.El
+.Sh SEE ALSO
+.Xr ioctl 2 ,
+.Xr mem 4 ,
+.Xr pctr 4 ,
+.Xr xf86 4 ,
+.Xr memconfig 8
+.Sh HISTORY
+.Nm
+support was originally included in
+.Fx 3.3 .
diff --git a/static/openbsd/man4/man4.amd64/nvram.4 b/static/openbsd/man4/man4.amd64/nvram.4
new file mode 100644
index 00000000..a7655d23
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/nvram.4
@@ -0,0 +1,52 @@
+.\"	$OpenBSD: nvram.4,v 1.1 2007/08/02 16:40:27 deraadt Exp $
+.\"
+.\" Copyright 2004 Joshua Stein <jcs@openbsd.org>
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
+.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
+.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
+.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
+.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
+.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
+.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+.\"
+.Dd $Mdocdate: August 2 2007 $
+.Dt NVRAM 4 amd64
+.Os
+.Sh NAME
+.Nm nvram
+.Nd driver for reading PC NVRAM contents
+.Sh SYNOPSIS
+.Cd "pseudo-device nvram 1"
+.Sh DESCRIPTION
+The
+.Nm
+device provides read-only access to the non-volatile memory contained in the
+MC146818 real-time clock.
+.Pp
+This data is provided as a seekable character device,
+.Pa /dev/nvram .
+Checksums of the NVRAM contents are calculated over bytes 2 to 31 and stored
+in byte 32.
+A valid checksum is required for the driver to initialize.
+.Sh FILES
+.Bl -tag -width /dev/nvram
+.It Pa /dev/nvram
+.El
+.Sh HISTORY
+.Nm
+support was originally included in
+.Ox 3.7 .
diff --git a/static/openbsd/man4/man4.amd64/pctr.4 b/static/openbsd/man4/man4.amd64/pctr.4
new file mode 100644
index 00000000..c024acc4
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/pctr.4
@@ -0,0 +1,234 @@
+.\"	$OpenBSD: pctr.4,v 1.8 2019/10/05 20:53:49 matthieu Exp $
+.\"
+.\" Pentium performance counter driver for OpenBSD.
+.\" Copyright 1996 David Mazieres <dm@lcs.mit.edu>.
+.\"
+.\" Modification and redistribution in source and binary forms is
+.\" permitted provided that due credit is given to the author and the
+.\" OpenBSD project by leaving this copyright notice intact.
+.\"
+.Dd $Mdocdate: October 5 2019 $
+.Dt PCTR 4 amd64
+.Os
+.Sh NAME
+.Nm pctr
+.Nd driver for CPU performance counters
+.Sh SYNOPSIS
+.Cd "pseudo-device pctr 1"
+.Sh DESCRIPTION
+The
+.Nm
+device provides access to the performance counters on AMD and Intel brand
+processors, and to the TSC on others.
+.Pp
+Intel processors have two 40-bit performance counters which can be
+programmed to count events such as cache misses, branch target buffer hits,
+TLB misses, dual-issues, interrupts, pipeline flushes, and more.
+While AMD processors have four 48-bit counters, their precision is decreased
+to 40 bits.
+.Pp
+There is one
+.Em ioctl
+call to read the status of all counters, and one
+.Em ioctl
+call to program the function of each counter.
+All require the following includes:
+.Bd -literal -offset indent
+#include <sys/types.h>
+#include <machine/cpu.h>
+#include <machine/pctr.h>
+.Ed
+.Pp
+The current state of all counters can be read with the
+.Dv PCIOCRD
+.Em ioctl ,
+which takes an argument of type
+.Dv "struct pctrst" :
+.Bd -literal -offset indent
+#define PCTR_NUM	4
+struct pctrst {
+	u_int pctr_fn[PCTR_NUM];
+	pctrval pctr_tsc;
+	pctrval pctr_hwc[PCTR_NUM];
+};
+.Ed
+.Pp
+In this structure,
+.Em ctr_fn
+contains the functions of the counters, as previously set by the
+.Dv PCIOCS0 ,
+.Dv PCIOCS1 ,
+.Dv PCIOCS2
+and
+.Dv PCIOCS3
+ioctls (see below).
+.Em pctr_hwc
+contains the actual value of the hardware counters.
+.Em pctr_tsc
+is a free-running, 64-bit cycle counter.
+.Pp
+The functions of the counters can be programmed with ioctls
+.Dv PCIOCS0 ,
+.Dv PCIOCS1 ,
+.Dv PCIOCS2
+and
+.Dv PCIOCS3
+which require a writeable file descriptor and take an argument of type
+.Dv "unsigned int" . \&
+The meaning of this integer is dependent on the particular CPU.
+.Ss Time stamp counter
+The time stamp counter is available on most of the AMD and Intel CPUs.
+It is set to zero at boot time, and then increments with each cycle.
+Because the counter is 64-bits wide, it does not overflow.
+.Pp
+The value of the time stamp counter is returned by the
+.Dv PCIOCRD
+.Em ioctl ,
+so that one can get an exact timestamp on readings of the hardware
+event counters.
+.Pp
+The performance counters can be read directly from user-mode without
+need to invoke the kernel.
+The macro
+.Fn rdpmc ctr
+takes 0, 1, 2 or 3 as an argument to specify a counter, and returns that
+counter's 40-bit value (which will be of type
+.Em pctrval ) .
+This is generally preferable to making a system call as it introduces
+less distortion in measurements.
+.Pp
+Counter functions supported by these CPUs contain several parts.
+The most significant byte (an 8-bit integer shifted left by
+.Dv PCTR_CM_SHIFT )
+contains a
+.Em "counter mask" .
+If non-zero, this sets a threshold for the number of times an event
+must occur in one cycle for the counter to be incremented.
+The
+.Em "counter mask"
+can therefore be used to count cycles in which an event
+occurs at least some number of times.
+The next byte contains several flags:
+.Bl -tag -width PCTR_EN
+.It Dv PCTR_U
+Enables counting of events that occur in user mode.
+.It Dv PCTR_K
+Enables counting of events that occur in kernel mode.
+You must set at least one of
+.Dv PCTR_K
+and
+.Dv PCTR_U
+to count anything.
+.It Dv PCTR_E
+Counts edges rather than cycles.
+For some functions this allows you
+to get an estimate of the number of events rather than the number of
+cycles occupied by those events.
+.It Dv PCTR_EN
+Enable counters.
+This bit must be set in the function for counter 0
+in order for either of the counters to be enabled.
+This bit should probably be set in counter 1 as well.
+.It Dv PCTR_I
+Inverts the sense of the
+.Em "counter mask" . \&
+When this bit is set, the counter only increments on cycles in which
+there are no
+.Em more
+events than specified in the
+.Em "counter mask" .
+.El
+.Pp
+The next byte (shifted left by the
+.Dv PCTR_UM_SHIFT )
+contains flags specific to the event being counted, also known as the
+.Em "unit mask" .
+.Pp
+For events dealing with the L2 cache, the following flags are valid
+on Intel brand processors:
+.Bl -tag -width PCTR_UM_M
+.It Dv PCTR_UM_M
+Count events involving modified cache coherency state lines.
+.It Dv PCTR_UM_E
+Count events involving exclusive cache coherency state lines.
+.It Dv PCTR_UM_S
+Count events involving shared cache coherency state lines.
+.It Dv PCTR_UM_I
+Count events involving invalid cache coherency state lines.
+.El
+.Pp
+To measure all L2 cache activity, all these bits should be set.
+They can be set with the macro
+.Dv PCTR_UM_MESI
+which contains the bitwise or of all of the above.
+.Pp
+For event types dealing with bus transactions, there is another flag
+that can be set in the
+.Em "unit mask" :
+.Bl -tag -width PCTR_UM_A
+.It Dv PCTR_UM_A
+Count all appropriate bus events, not just those initiated by the
+processor.
+.El
+.Pp
+Events marked
+.Em (MESI)
+require the
+.Dv PCTR_UM_[MESI]
+bits in the
+.Em "unit mask" . \&
+Events marked
+.Em (A)
+can take the
+.Dv PCTR_UM_A
+bit.
+.Pp
+Finally, the least significant byte of the counter function is the
+event type to count.
+A list of possible event functions could be obtained by running a
+.Xr pctr 1
+command with
+.Fl l
+option.
+.Sh FILES
+.Bl -tag -width /dev/pctr -compact
+.It Pa /dev/pctr
+.El
+.Sh ERRORS
+.Bl -tag -width "[ENODEV]"
+.It Bq Er ENODEV
+An attempt was made to set the counter functions on a CPU that does
+not support counters.
+.It Bq Er EINVAL
+An invalid counter function was provided as an argument to the
+.Dv PCIOCSx
+.Em ioctl .
+.It Bq Er EPERM
+An attempt was made to set the counter functions, but the device was
+not open for writing.
+.El
+.Sh SEE ALSO
+.Xr pctr 1 ,
+.Xr ioctl 2
+.Sh HISTORY
+A
+.Nm
+device first appeared in
+.Ox 2.0 .
+Support for amd64 architecture appeared in
+.Ox 4.3 .
+.Sh AUTHORS
+.An -nosplit
+The
+.Nm
+device was written by
+.An David Mazieres Aq Mt dm@lcs.mit.edu .
+Support for amd64 architecture was written by
+.An Mike Belopuhov Aq Mt mikeb@openbsd.org .
+.Sh BUGS
+Not all counter functions are completely accurate.
+Some of the functions may not make any sense at all.
+Also you should be aware of the possibility of an interrupt between
+invocations of
+.Fn rdpmc
+that can potentially decrease the accuracy of measurements.
diff --git a/static/openbsd/man4/man4.amd64/skgpio.4 b/static/openbsd/man4/man4.amd64/skgpio.4
new file mode 100644
index 00000000..eaa494ea
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/skgpio.4
@@ -0,0 +1,57 @@
+.\"     $OpenBSD: skgpio.4,v 1.2 2015/10/22 11:01:14 sobrado Exp $
+.\"
+.\" Copyright (c) 2014 Matt Dainty <matt@bodgit-n-scarper.com>
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.Dd $Mdocdate: October 22 2015 $
+.Dt SKGPIO 4 amd64
+.Os
+.Sh NAME
+.Nm skgpio
+.Nd Soekris net6501 GPIO and LEDs
+.Sh SYNOPSIS
+.Cd "skgpio0 at isa? port 0x680"
+.Cd "gpio* at skgpio?"
+.Sh DESCRIPTION
+The
+.Nm
+driver provides support for the GPIO and LEDs as implemented by the Xilinx
+Spartan FGPA integrated into the Soekris net6501 programmed with the default
+bitstream found in the BIOS.
+.Pp
+Two standard
+.Xr gpio 4
+interfaces are provided, one for the 16 real pins which can be configured as
+either inputs or outputs and another with 2 output-only pins that map
+to the error and ready LEDs respectively.
+Both may be used with
+.Xr gpioctl 8 .
+.Sh SEE ALSO
+.Xr gpio 4 ,
+.Xr intro 4 ,
+.Xr isa 4 ,
+.Xr gpioctl 8
+.Sh HISTORY
+The
+.Nm
+driver first appeared in
+.Ox 5.7 .
+.Sh AUTHORS
+The
+.Nm
+driver was written by
+.An Matt Dainty Aq matt@bodgit-n-scarper.com .
+.Sh BUGS
+If the Xilinx FPGA is programmed with a different bitstream, the driver will
+likely not function.
diff --git a/static/openbsd/man4/man4.amd64/tcpcib.4 b/static/openbsd/man4/man4.amd64/tcpcib.4
new file mode 100644
index 00000000..327e6f19
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/tcpcib.4
@@ -0,0 +1,71 @@
+.\"     $OpenBSD: tcpcib.4,v 1.6 2014/11/15 14:41:02 bentley Exp $
+.\"
+.\" Copyright (c) 2012 Matt Dainty <matt@bodgit-n-scarper.com>
+.\"
+.\" Permission to use, copy, modify, and distribute this software for any
+.\" purpose with or without fee is hereby granted, provided that the above
+.\" copyright notice and this permission notice appear in all copies.
+.\"
+.\" THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\" WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\" MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\" ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\" WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.Dd $Mdocdate: November 15 2014 $
+.Dt TCPCIB 4 amd64
+.Os
+.Sh NAME
+.Nm tcpcib
+.Nd Intel Atom E600 series LPC bridge, timecounter and watchdog timer
+.Sh SYNOPSIS
+.Cd "tcpcib* at pci?"
+.Cd "isa* at tcpcib?"
+.Sh DESCRIPTION
+The
+.Nm
+driver provides support for the Intel Atom E600 series LPC bridge and
+implements a 64-bit 14.3 MHz timecounter using the HPET timer.
+.Pp
+The
+.Nm
+driver also provides the standard
+.Xr watchdog 4
+interface to the watchdog timer and may be used with
+.Xr watchdogd 8 .
+The watchdog timer can be configured via
+.Xr sysctl 8 .
+.Pp
+Once the watchdog timer resets the CPU, the driver reports it on the
+next boot displaying the
+.Dq reboot on timeout
+message in the
+.Xr dmesg 8 .
+.Pp
+The maximum timeout value supported by the watchdog timer is 600
+seconds.
+.Sh SEE ALSO
+.Xr intro 4 ,
+.Xr isa 4 ,
+.Xr pci 4 ,
+.Xr watchdog 4 ,
+.Xr sysctl 8 ,
+.Xr watchdogd 8
+.Sh HISTORY
+The
+.Nm
+driver first appeared in
+.Ox 5.2 .
+.Sh AUTHORS
+The
+.Nm
+driver was written by
+.An Matt Dainty Aq Mt matt@bodgit-n-scarper.com .
+.Sh BUGS
+Apart from the core
+.Xr pcib 4
+functionality, timecounter and the
+.Xr watchdog 4
+interface, the driver doesn't support any other aspects of the hardware.
diff --git a/static/openbsd/man4/man4.amd64/vmm.4 b/static/openbsd/man4/man4.amd64/vmm.4
new file mode 100644
index 00000000..cc621a8e
--- /dev/null
+++ b/static/openbsd/man4/man4.amd64/vmm.4
@@ -0,0 +1,122 @@
+.\"	$OpenBSD: vmm.4,v 1.10 2024/11/05 15:08:46 mlarkin Exp $
+.\"
+.\"Copyright (c) 2015 Mike Larkin <mlarkin@openbsd.org>
+.\"
+.\"Permission to use, copy, modify, and distribute this software for any
+.\"purpose with or without fee is hereby granted, provided that the above
+.\"copyright notice and this permission notice appear in all copies.
+.\"
+.\"THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
+.\"WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
+.\"MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
+.\"ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\"WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
+.\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
+.\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\"
+.Dd $Mdocdate: November 5 2024 $
+.Dt VMM 4 amd64
+.Os
+.Sh NAME
+.Nm vmm
+.Nd virtual machine monitor
+.Sh SYNOPSIS
+.Cd "vmm0    at mainbus0"
+.Pp
+.In machine/vmmvar.h
+.Sh DESCRIPTION
+The
+.Nm
+driver implements a virtual machine monitor (VMM) suitable for executing
+.Em virtual machines
+(VMs).
+A VMM runs on the
+.Em host
+operating system and provides facilities to execute one or more
+VMs, each of which is provided with a suitable complement of
+virtual hardware.
+.Pp
+These VMs run independently of the host, but may interact with
+it as any other machine would (e.g. via network communications or
+other means).
+.Pp
+VMs are allocated hardware resources by the VMM during creation,
+including:
+.Pp
+.Bl -bullet -offset indent -compact
+.It
+Virtual CPUs
+.It
+Virtual network interfaces
+.It
+Virtual disk images
+.It
+Virtual serial ports
+.El
+.Pp
+Although VMs execute independently of each other and the host, they
+do consume host resources and, as such, the number of VMs (and their
+configurations) should be taken into consideration when planning
+host capacity.
+.Pp
+The
+.Nm
+driver requires suitable host CPU capabilities in order to provide
+VM services.
+The
+.Nm
+driver requires at least one CPU with hardware-assisted virtualization
+capabilities and nested or extended paging capabilities to be
+present on the host.
+For more information, consult the CPU vendor's documentation.
+.Pp
+The following
+.Xr ioctl 2
+commands are provided for managing
+.Nm
+guests:
+.Bl -tag -width Ds -offset indent
+.It Dv VMM_IOC_CREATE Fa "struct vm_create_params *"
+Create a VM, initializing
+.Nm
+if not yet started.
+(Does not start the VCPU.)
+.It Dv VMM_IOC_RUN Fa "struct vm_run_params *"
+Run a VCPU for a defined VM.
+Return on VM-exit, when the VCPU stopped, or an error occurred.
+.It Dv VMM_IOC_INFO Fa "struct vm_info_params *"
+Get information about the VMs currently hosted by
+.Nm .
+.It Dv VMM_IOC_TERM Fa "struct vm_terminate_params *"
+Terminate a given VM.
+.It Dv VMM_IOC_RESETCPU Fa "struct vm_resetcpu_params *"
+Reset a VCPU to power-on-init state using the provided register state.
+.It Dv VMM_IOC_INTR Fa "struct vm_intr_params *"
+Signal a pending interrupt for a VCPU.
+.It Dv VMM_IOC_READREGS Fa "struct vm_rwregs_params *"
+Read registers of a VCPU.
+.It Dv VMM_IOC_WRITEREGS Fa "struct vm_rwregs_params *"
+Write register values of a VCPU.
+.It Dv VMM_IOC_READVMPARAMS Fa "struct vm_rwvmparams_params *"
+Read paravirtualized hardware parameters (such as
+.Xr pvclock 4
+version) for a VM.
+.It Dv VMM_IOC_WRITEVMPARAMS Fa "struct vm_rwvmparams_params *"
+Write paravirtualized hardware parameters (such as
+.Xr pvclock 4
+guest physical address) for a VM.
+.El
+.Sh SEE ALSO
+.Xr cpu 4 ,
+.Xr intro 4 ,
+.Xr virtio 4 ,
+.Xr vmctl 8 ,
+.Xr vmd 8
+.Sh HISTORY
+The
+.Nm
+driver
+appeared in
+.Ox 5.9 .
+.Sh AUTHORS
+.An Mike Larkin Aq Mt mlarkin@openbsd.org