summaryrefslogtreecommitdiff
path: root/usr/src/uts/common/os
diff options
context:
space:
mode:
Diffstat (limited to 'usr/src/uts/common/os')
-rw-r--r--usr/src/uts/common/os/cap_util.c2
-rw-r--r--usr/src/uts/common/os/clock_process.c2
-rw-r--r--usr/src/uts/common/os/ddi.c4
-rw-r--r--usr/src/uts/common/os/ddi_hp_impl.c12
-rw-r--r--usr/src/uts/common/os/ddi_ufm.c2
-rw-r--r--usr/src/uts/common/os/ddifm.c4
-rw-r--r--usr/src/uts/common/os/devid_cache.c6
-rw-r--r--usr/src/uts/common/os/errorq.c2
-rw-r--r--usr/src/uts/common/os/exit.c14
-rw-r--r--usr/src/uts/common/os/fm.c2
-rw-r--r--usr/src/uts/common/os/kmem.c2
-rw-r--r--usr/src/uts/common/os/ksensor.c4
-rw-r--r--usr/src/uts/common/os/logsubr.c4
-rw-r--r--usr/src/uts/common/os/ndifm.c4
-rw-r--r--usr/src/uts/common/os/priv_defs6
-rw-r--r--usr/src/uts/common/os/rctl.c4
-rw-r--r--usr/src/uts/common/os/streamio.c2
-rw-r--r--usr/src/uts/common/os/sunpm.c16
-rw-r--r--usr/src/uts/common/os/timer.c4
19 files changed, 48 insertions, 48 deletions
diff --git a/usr/src/uts/common/os/cap_util.c b/usr/src/uts/common/os/cap_util.c
index 86475315e1..7647302cfe 100644
--- a/usr/src/uts/common/os/cap_util.c
+++ b/usr/src/uts/common/os/cap_util.c
@@ -693,7 +693,7 @@ cu_cpc_program(cpu_t *cp, int *err)
*
* Context is marked with KCPC_CTX_INVALID_STOPPED when context is
* unprogrammed and may be marked with KCPC_CTX_INVALID when
- * kcpc_invalidate_all() is called by cpustat(1M) and dtrace CPC to
+ * kcpc_invalidate_all() is called by cpustat(8) and dtrace CPC to
* invalidate all CPC contexts before they take over all the counters.
*
* This isn't necessary since these flags are only used for thread bound
diff --git a/usr/src/uts/common/os/clock_process.c b/usr/src/uts/common/os/clock_process.c
index 555cfd01d9..a3c1641c9c 100644
--- a/usr/src/uts/common/os/clock_process.c
+++ b/usr/src/uts/common/os/clock_process.c
@@ -18,7 +18,7 @@
* clock. This clock is weakly defined by POSIX as "The identifier of the
* CPU-time clock associated with the process making a clock() or timer*()
* function call". We interpret that as including LMS_USER, LMS_SYSTEM, and
- * LMS_TRAP microstates. This is similar to what we do in proc(4) for the
+ * LMS_TRAP microstates. This is similar to what we do in proc(5) for the
* lwpstatus_t and the prstatus_t.
*
* At this time, we only provide the ability to read the current time (e.g.
diff --git a/usr/src/uts/common/os/ddi.c b/usr/src/uts/common/os/ddi.c
index a37d91e92a..c348ee474c 100644
--- a/usr/src/uts/common/os/ddi.c
+++ b/usr/src/uts/common/os/ddi.c
@@ -1136,8 +1136,8 @@ qunbufcall(queue_t *q, bufcall_id_t id)
* Associate the stream with an instance of the bottom driver. This
* function is called by APIs that establish or modify the hardware
* association (ppa) of an open stream. Two examples of such
- * post-open(9E) APIs are the dlpi(7p) DL_ATTACH_REQ message, and the
- * ndd(1M) "instance=" ioctl(2). This interface may be called from a
+ * post-open(9E) APIs are the dlpi(4P) DL_ATTACH_REQ message, and the
+ * ndd(8) "instance=" ioctl(2). This interface may be called from a
* stream driver's wput procedure and from within syncq perimeters,
* so it can't block.
*
diff --git a/usr/src/uts/common/os/ddi_hp_impl.c b/usr/src/uts/common/os/ddi_hp_impl.c
index 38e575dbfd..8f0890fc2b 100644
--- a/usr/src/uts/common/os/ddi_hp_impl.c
+++ b/usr/src/uts/common/os/ddi_hp_impl.c
@@ -92,8 +92,8 @@
* - Through the nexus driver interface, ndi_hp_state_change_req. PCIe
* nexus drivers that pass a hotplug interrupt through to pciehpc will kick
* off state changes in this way.
- * - Through coordinated removal, ddihp_modctl. Both cfgadm(1M) and
- * hotplug(1M) pass state change requests through hotplugd, which uses
+ * - Through coordinated removal, ddihp_modctl. Both cfgadm(8) and
+ * hotplug(8) pass state change requests through hotplugd, which uses
* modctl to request state changes to the DDI hotplug framework. That
* interface is ultimately implemented by ddihp_modctl.
*
@@ -131,7 +131,7 @@
* of some key components are below.
*
* +------------+
- * | cfgadm(1M) |
+ * | cfgadm(8) |
* +------------+
* |
* +-------------------+
@@ -139,7 +139,7 @@
* +-------------------+
* |
* +-------------+ +------------+
- * | hotplug(1M) |----------| libhotplug |
+ * | hotplug(8) |----------| libhotplug |
* +-------------+ +------------+
* |
* +----------+
@@ -193,14 +193,14 @@
*
* KEY HOTPLUG SOFTWARE COMPONENTS
*
- * CFGADM(1M)
+ * cfgadm(8)
*
* cfgadm is the canonical tool for hotplug operations. It can be used to
* list connections on the system and change their state in a coordinated
* fashion. For more information, see its manual page.
*
*
- * HOTPLUG(1M)
+ * hotplug(8)
*
* hotplug is a command line tool for managing hotplug connections for
* connectors. For more information, see its manual page.
diff --git a/usr/src/uts/common/os/ddi_ufm.c b/usr/src/uts/common/os/ddi_ufm.c
index 3610df8bac..940ebf82bf 100644
--- a/usr/src/uts/common/os/ddi_ufm.c
+++ b/usr/src/uts/common/os/ddi_ufm.c
@@ -30,7 +30,7 @@
* drivers that participate in the DDI UFM subsystem on a per-instance basis
* via ddi_ufm_handle_t structures (see ddi_ufm_impl.h). This is known as the
* UFM handle. The UFM handle contains a pointer to the driver's UFM ops,
- * which the ufm(7D) pseudo driver uses to invoke the UFM entry points in
+ * which the ufm(4D) pseudo driver uses to invoke the UFM entry points in
* response to DDI UFM ioctls. Additionally, the DDI UFM subsystem uses the
* handle to maintain cached UFM image and slot data.
*
diff --git a/usr/src/uts/common/os/ddifm.c b/usr/src/uts/common/os/ddifm.c
index 533fa15aed..dc39ba49ab 100644
--- a/usr/src/uts/common/os/ddifm.c
+++ b/usr/src/uts/common/os/ddifm.c
@@ -56,7 +56,7 @@
*
* Error reports resulting from hardware component specific and common IO
* fault and driver defects must be accompanied by an Eversholt fault
- * tree (.eft) by the Solaris fault manager (fmd(1M)) for
+ * tree (.eft) by the Solaris fault manager (fmd(8)) for
* diagnosis.
*
* DDI_FM_ERRCB_CAPABLE
@@ -466,7 +466,7 @@ out: if (ereport && (nva == NULL))
/*
* Generate an error report for consumption by the Solaris Fault Manager,
- * fmd(1M). Valid ereport classes are defined in /usr/include/sys/fm/io.
+ * fmd(8). Valid ereport classes are defined in /usr/include/sys/fm/io.
*
* The ENA should be set if this error is a result of an error status
* returned from ddi_dma_err_check() or ddi_acc_err_check(). Otherwise,
diff --git a/usr/src/uts/common/os/devid_cache.c b/usr/src/uts/common/os/devid_cache.c
index 3e1a06a844..2a780eebe2 100644
--- a/usr/src/uts/common/os/devid_cache.c
+++ b/usr/src/uts/common/os/devid_cache.c
@@ -47,7 +47,7 @@
* involves walking the entire device tree attaching all possible disk
* instances, to search for the device referenced by a devid. Obviously,
* full device discovery is something to be avoided where possible.
- * Note that simply invoking devfsadm(1M) is equivalent to running full
+ * Note that simply invoking devfsadm(8) is equivalent to running full
* discovery at the devid cache level.
*
* Reasons why a disk may not be accessible:
@@ -61,7 +61,7 @@
* When discovery may succeed:
* Discovery will result in success when a device has been moved
* to a different address. Note that it's recommended that
- * devfsadm(1M) be invoked (no arguments required) whenever a system's
+ * devfsadm(8) be invoked (no arguments required) whenever a system's
* h/w configuration has been updated. Alternatively, a
* reconfiguration boot can be used to accomplish the same result.
*
@@ -69,7 +69,7 @@
* failure for a device which was powered off. Assuming the cache has an
* entry for such a device, simply powering it on should permit the system
* to access it. If problems persist after powering it on, invoke
- * devfsadm(1M).
+ * devfsadm(8).
*
* Discovery prior to mounting root is only of interest when booting
* from a filesystem which accesses devices by device id, which of
diff --git a/usr/src/uts/common/os/errorq.c b/usr/src/uts/common/os/errorq.c
index 8b41e7e8c1..cd71b9be08 100644
--- a/usr/src/uts/common/os/errorq.c
+++ b/usr/src/uts/common/os/errorq.c
@@ -946,7 +946,7 @@ errorq_cancel(errorq_t *eqp, errorq_elem_t *eqep)
/*
* Write elements on the dump list of each nvlist errorq to the dump device.
- * Upon reboot, fmd(1M) will extract and replay them for diagnosis.
+ * Upon reboot, fmd(8) will extract and replay them for diagnosis.
*/
void
errorq_dump(void)
diff --git a/usr/src/uts/common/os/exit.c b/usr/src/uts/common/os/exit.c
index 317251f12d..5a9355ae9f 100644
--- a/usr/src/uts/common/os/exit.c
+++ b/usr/src/uts/common/os/exit.c
@@ -170,11 +170,11 @@ restart_init(int what, int why)
* zone) know that init has failed and will be restarted.
*/
zcmn_err(p->p_zone->zone_id, CE_WARN,
- "init(1M) %s: restarting automatically",
+ "init(8) %s: restarting automatically",
exit_reason(reason_buf, sizeof (reason_buf), what, why));
if (!INGLOBALZONE(p)) {
- cmn_err(CE_WARN, "init(1M) for zone %s (pid %d) %s: "
+ cmn_err(CE_WARN, "init(8) for zone %s (pid %d) %s: "
"restarting automatically",
p->p_zone->zone_name, p->p_pid, reason_buf);
}
@@ -189,7 +189,7 @@ restart_init(int what, int why)
/*
* Grab p_lock and begin clearing miscellaneous global process
- * state that needs to be reset before we exec the new init(1M).
+ * state that needs to be reset before we exec the new init(8).
*/
mutex_enter(&p->p_lock);
@@ -287,7 +287,7 @@ restart_init(int what, int why)
(void) freectty(B_TRUE);
/*
- * Now exec() the new init(1M) on top of the current process. If we
+ * Now exec() the new init(8) on top of the current process. If we
* succeed, the caller will treat this like a successful system call.
* If we fail, we issue messages and the caller will proceed with exit.
*/
@@ -297,11 +297,11 @@ restart_init(int what, int why)
return (0);
zcmn_err(p->p_zone->zone_id, CE_WARN,
- "failed to restart init(1M) (err=%d): system reboot required", err);
+ "failed to restart init(8) (err=%d): system reboot required", err);
if (!INGLOBALZONE(p)) {
- cmn_err(CE_WARN, "failed to restart init(1M) for zone %s "
- "(pid %d, err=%d): zoneadm(1M) boot required",
+ cmn_err(CE_WARN, "failed to restart init(8) for zone %s "
+ "(pid %d, err=%d): zoneadm(8) boot required",
p->p_zone->zone_name, p->p_pid, err);
}
diff --git a/usr/src/uts/common/os/fm.c b/usr/src/uts/common/os/fm.c
index 15215b58c3..bd3e5dceac 100644
--- a/usr/src/uts/common/os/fm.c
+++ b/usr/src/uts/common/os/fm.c
@@ -364,7 +364,7 @@ fm_nvprint(nvlist_t *nvl)
/*
* Wrapper for panic() that first produces an FMA-style message for admins.
- * Normally such messages are generated by fmd(1M)'s syslog-msgs agent: this
+ * Normally such messages are generated by fmd(8)'s syslog-msgs agent: this
* is the one exception to that rule and the only error that gets messaged.
* This function is intended for use by subsystems that have detected a fatal
* error and enqueued appropriate ereports and wish to then force a panic.
diff --git a/usr/src/uts/common/os/kmem.c b/usr/src/uts/common/os/kmem.c
index 0082baed7a..394235f26c 100644
--- a/usr/src/uts/common/os/kmem.c
+++ b/usr/src/uts/common/os/kmem.c
@@ -2250,7 +2250,7 @@ kmem_dumppr(char **pp, char *e, const char *format, ...)
}
/*
- * Called when dumpadm(1M) configures dump parameters.
+ * Called when dumpadm(8) configures dump parameters.
*/
void
kmem_dump_init(size_t size)
diff --git a/usr/src/uts/common/os/ksensor.c b/usr/src/uts/common/os/ksensor.c
index 491fbcc7cd..7dd4a22c8a 100644
--- a/usr/src/uts/common/os/ksensor.c
+++ b/usr/src/uts/common/os/ksensor.c
@@ -67,8 +67,8 @@
*
* The implementation of (1) is all in this file. The implementation of (2) is
* in uts/common/io/ksensor/ksensor_drv.c. The implementation of (3) is found in
- * all of the different leaf devices. Examples of (3) include pchtemp(7D) and
- * igb(7D).
+ * all of the different leaf devices. Examples of (3) include pchtemp(4D) and
+ * igb(4D).
*
* We separate numbers one and two into two different components for a few
* reasons. The most important thing is that drivers that provide sensors should
diff --git a/usr/src/uts/common/os/logsubr.c b/usr/src/uts/common/os/logsubr.c
index f597c4a922..b5f41d93f9 100644
--- a/usr/src/uts/common/os/logsubr.c
+++ b/usr/src/uts/common/os/logsubr.c
@@ -198,7 +198,7 @@ log_init(void)
/*
* Create a backlog queue to consume console messages during periods
- * when there is no console reader (e.g. before syslogd(1M) starts).
+ * when there is no console reader (e.g. before syslogd(8) starts).
*/
log_backlogq = log_consq = log_makeq(0, LOG_HIWAT, NULL);
@@ -681,7 +681,7 @@ log_sendmsg(mblk_t *mp, zoneid_t zoneid)
if (lp->log_q == log_consq) {
console_printf(log_overflow_msg,
lp->log_minor,
- " -- is syslogd(1M) running?");
+ " -- is syslogd(8) running?");
} else {
printf(log_overflow_msg,
lp->log_minor, "");
diff --git a/usr/src/uts/common/os/ndifm.c b/usr/src/uts/common/os/ndifm.c
index 16613a9203..54640971fd 100644
--- a/usr/src/uts/common/os/ndifm.c
+++ b/usr/src/uts/common/os/ndifm.c
@@ -669,7 +669,7 @@ ndi_fm_dma_err_set(ddi_dma_handle_t handle, ddi_fm_error_t *dfe)
/*
* Call parent busop fm initialization routine.
*
- * Called during driver attach(1M)
+ * Called during driver attach(9E)
*/
int
i_ndi_busop_fm_init(dev_info_t *dip, int tcap, ddi_iblock_cookie_t *ibc)
@@ -696,7 +696,7 @@ i_ndi_busop_fm_init(dev_info_t *dip, int tcap, ddi_iblock_cookie_t *ibc)
/*
* Call parent busop fm clean-up routine.
*
- * Called during driver detach(1M)
+ * Called during driver detach(9E)
*/
void
i_ndi_busop_fm_fini(dev_info_t *dip)
diff --git a/usr/src/uts/common/os/priv_defs b/usr/src/uts/common/os/priv_defs
index bc1787c9ca..186aafc460 100644
--- a/usr/src/uts/common/os/priv_defs
+++ b/usr/src/uts/common/os/priv_defs
@@ -213,7 +213,7 @@ privilege PRIV_NET_BINDMLP
Allow a process to bind to a port that is configured as a
multi-level port(MLP) for the process's zone. This privilege
applies to both shared address and zone-specific address MLPs.
- See tnzonecfg(4) from the Trusted Extensions manual pages for
+ See tnzonecfg(5) from the Trusted Extensions manual pages for
information on configuring MLP ports.
This privilege is interpreted only if the system is configured
with Trusted Extensions.
@@ -499,7 +499,7 @@ privilege PRIV_SYS_TRANS_LABEL
privilege PRIV_VIRT_MANAGE
Allows a process to manage virtualized environments such as
- xVM(5).
+ xVM(7).
privilege PRIV_WIN_COLORMAP
@@ -605,7 +605,7 @@ privilege PRIV_WIN_UPGRADE_SL
privilege PRIV_XVM_CONTROL
- Allows a process access to the xVM(5) control devices for
+ Allows a process access to the xVM(7) control devices for
managing guest domains and the hypervisor. This privilege is
used only if booted into xVM on x86 platforms.
diff --git a/usr/src/uts/common/os/rctl.c b/usr/src/uts/common/os/rctl.c
index 226ec844f9..81a1b5454a 100644
--- a/usr/src/uts/common/os/rctl.c
+++ b/usr/src/uts/common/os/rctl.c
@@ -148,7 +148,7 @@
* The locking subsequence of interest is: p_lock, rctl_dict_lock,
* rctl_lists_lock, entity->rcs_lock.
*
- * The projects(4) database and project entity resource controls
+ * The project(5) database and project entity resource controls
* A special case is made for RCENTITY_PROJECT values set through the
* setproject(3PROJECT) interface. setproject() makes use of a private
* interface, setprojrctl(), which passes through an array of resource control
@@ -169,7 +169,7 @@
*
* rctl->rc_values - a linked list of rctl_val_t. These are the active
* resource values associated with this rctl, and may have been set by
- * setrctl() - via prctl(1M), or by setprojrctl() - via
+ * setrctl() - via prctl(1), or by setprojrctl() - via
* setproject(3PROJECT).
*
* rctl->rc_projdb - a linked list of rctl_val_t. These reflect the
diff --git a/usr/src/uts/common/os/streamio.c b/usr/src/uts/common/os/streamio.c
index 11a4033db1..c137a498d1 100644
--- a/usr/src/uts/common/os/streamio.c
+++ b/usr/src/uts/common/os/streamio.c
@@ -3627,7 +3627,7 @@ strioctl(struct vnode *vp, int cmd, intptr_t arg, int flag, int copyflag,
/*
* The I_STR facility provides a trap door for malicious
- * code to send down bogus streamio(7I) ioctl commands to
+ * code to send down bogus streamio(4I) ioctl commands to
* unsuspecting STREAMS modules and drivers which expect to
* only get these messages from the stream head.
* Explicitly prohibit any streamio ioctls which can be
diff --git a/usr/src/uts/common/os/sunpm.c b/usr/src/uts/common/os/sunpm.c
index 0d40abbbcf..7518c45cea 100644
--- a/usr/src/uts/common/os/sunpm.c
+++ b/usr/src/uts/common/os/sunpm.c
@@ -61,8 +61,8 @@
* tells what each component's power state values are, and provides human
* readable strings (currently unused) for each component name and power state.
* Devices which export pm-components(9P) are automatically power managed
- * whenever autopm is enabled (via PM_START_PM ioctl issued by pmconfig(1M)
- * after parsing power.conf(4)). The exception to this rule is that power
+ * whenever autopm is enabled (via PM_START_PM ioctl issued by pmconfig(8)
+ * after parsing power.conf(5)). The exception to this rule is that power
* manageable CPU devices may be automatically managed independently of autopm
* by either enabling or disabling (via PM_START_CPUPM and PM_STOP_CPUPM
* ioctls) cpupm. If the CPU devices are not managed independently, then they
@@ -72,13 +72,13 @@
* hardware state.
*
* Each device component also has a threshold time associated with each power
- * transition (see power.conf(4)), and a busy/idle state maintained by the
+ * transition (see power.conf(5)), and a busy/idle state maintained by the
* driver calling pm_idle_component(9F) and pm_busy_component(9F).
* Components are created idle.
*
* The PM framework provides several functions:
- * -implement PM policy as described in power.conf(4)
- * Policy is set by pmconfig(1M) issuing pm ioctls based on power.conf(4).
+ * -implement PM policy as described in power.conf(5)
+ * Policy is set by pmconfig(8) issuing pm ioctls based on power.conf(5).
* Policies consist of:
* -set threshold values (defaults if none provided by pmconfig)
* -set dependencies among devices
@@ -122,7 +122,7 @@
* cdrom is always up whenever the console framebuffer is up, so that the user
* can insert a cdrom and see a popup as a result.
*
- * The dependency terminology used in power.conf(4) is not easy to understand,
+ * The dependency terminology used in power.conf(5) is not easy to understand,
* so we've adopted a different terminology in the implementation. We write
* of a "keeps up" and a "kept up" device. A relationship can be established
* where one device keeps up another. That means that if the keepsup device
@@ -384,7 +384,7 @@ int cpr_platform_enable = 0;
/*
* pm_S3_enabled indicates that we believe the platform can support S3,
- * which we get from pmconfig(1M)
+ * which we get from pmconfig(8)
*/
int pm_S3_enabled;
@@ -7646,7 +7646,7 @@ pm_cfb_setup(const char *stdout_path)
*/
} else {
cmn_err(CE_WARN, "Kernel debugger present: see "
- "kmdb(1M) for interaction with power management.");
+ "kmdb(1) for interaction with power management.");
}
}
#ifdef DEBUG
diff --git a/usr/src/uts/common/os/timer.c b/usr/src/uts/common/os/timer.c
index 7d061d878b..c78a545360 100644
--- a/usr/src/uts/common/os/timer.c
+++ b/usr/src/uts/common/os/timer.c
@@ -178,7 +178,7 @@ timer_delete_locked(proc_t *p, timer_t tid, itimer_t *it)
/*
* timer_grab() and its companion routine, timer_release(), are wrappers
- * around timer_lock()/_unlock() which allow the timer_*(3R) routines to
+ * around timer_lock()/_unlock() which allow the timer_*(3C) routines to
* (a) share error handling code and (b) not grab p_lock themselves. Routines
* which are called with p_lock held (e.g. timer_lwpbind(), timer_lwpexit())
* must call timer_lock()/_unlock() explictly.
@@ -193,7 +193,7 @@ timer_delete_locked(proc_t *p, timer_t tid, itimer_t *it)
* (a) The specified timer ID is out of range.
*
* (b) The specified timer ID does not correspond to a timer ID returned
- * from timer_create(3R).
+ * from timer_create(3C).
*
* (c) The specified timer ID is currently being removed.
*
generated by cgit v1.2.3 (git 2.46.0) at 2025-12-09 14:41:40 +0000