d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

mem(4): Improve ioctl section formatting

Browse Source 
Add the missing .El which fixes the indentation of the memory range
definitions and operation. Add subsection headings to further clarify
this section. Do the same for the RETURN VALUES section, and mention
explicitly that MEM_EXTRACT_PADDR always returns zero.

Reviewed by:	markj, 0mp, Pau Amma <pauamma@gundo.com>
Sponsored by:	Juniper Networks, Inc.
Sponsored by:	Klara, Inc.
MFC after:	3 days
Differential Revision:	https://reviews.freebsd.org/D34574
This commit is contained in:
Mitchell Horne 2022-02-24 12:15:17 -04:00
parent 393b7606f9
commit 071b78ce8f
1 changed files with 9 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
share/man/man4/mem.4
View File

@ -28,7 +28,7 @@
.\" @(#)mem.4 5.3 (Berkeley) 5/2/91
.\" $FreeBSD$
.\"
.Dd August 25, 2020
.Dd March 11, 2022
.Dt MEM 4
.Os
.Sh NAME
@ -65,6 +65,7 @@ is
long, and ends at virtual
address 0xf0000000.
.Sh IOCTL INTERFACE
.Ss Address Properties
The
.Dv MEM_EXTRACT_PADDR
ioctl can be used to look up the physical address and NUMA domain of a given
@ -104,6 +105,8 @@ The virtual address corresponds to a physical page mapping, and the
and
.Fa me_domain
fields are valid.
.El
.Ss Memory Ranges
.Pp
Several architectures allow attributes to be associated with ranges of physical
memory.
@ -200,6 +203,11 @@ to update an existing or establish a new range, or to
to remove a range.
.El
.Sh RETURN VALUES
.Ss MEM_EXTRACT_PADDR
The
.Dv MEM_EXTRACT_PADDR
ioctl always returns a value of zero.
.Ss MEMRANGE_GET/MEMRANGE_SET
.Bl -tag -width Er
.It Bq Er EOPNOTSUPP
Memory range operations are not supported on this architecture.