RAS-MC-CTL(8) RAS memory controller admin utility RAS-MC-CTL(8)NAME
ras-mc-ctl - RAS memory controller admin utility
SYNOPSIS
ras-mc-ctl [OPTION]...
DESCRIPTION
The ras-mc-ctl program is a perl(1) script which performs some useful RAS administration tasks on EDAC (Error Detection and Correction)
drivers.
OPTIONS --help Display a brief usage message.
--mainboard
Print mainboard vendor and model for this hardware, if available. The method used by ras-mc-ctl to obtain the mainboard vendor and
model information for the current system is described below in the MAINBOARD CONFIGURATION section.
--status
Print the status of EDAC drivers (loaded or unloaded).
--quiet
Be less verbose when executing an operation.
--register-labels
Register motherboard DIMM labels into EDAC driver sysfs files. This option uses the detected mainboard manufacturer and model num-
ber in combination with a "labels database" found in any of the files under /etc/ras/dimm_labels.d/* or in the labels.db file at
/etc/ras/dimm_labels.db. An entry for the current hardware must exist in the labels database for this option to do anything.
--print-labels
Display the configured labels for the current hardware, as well as the current labels registered with EDAC.
--guess-labels
Print DMI labels, when bank locator is available at the DMI table. It helps to fill the labels database at /etc/ras/dimm_labels.d/.
--labeldb=DB
Specify an alternate location for the labels database.
--delay=time
Specify a delay of ime seconds before registering dimm labels. Only meaninful if used together with --register-labels.
--layout
Prints the memory layout as detected by the EDAC driver. Useful to check if the EDAC driver is properly detecting the memory con-
troller architecture.
MAINBOARD CONFIGURATION
The ras-mc-ctl script uses the following method to determine the current system's mainboard vendor and model information:
1. If the config file /etc/edac/mainboard exists, then it is parsed by ras-mc-ctl. The mainboard config file has the following simple syn-
tax:
vendor = <mainboard vendor string>
model = <mainboard model string>
script = <script to gather mainboard information>
Where anything after a '#' character on a line is considered a comment. If the keyword script is specified, then that script or exe-
cutable is run by ras-mc-ctl to gather the mainboard vendor and model information. The script should write the resulting information on
stdout in the same format as the mainboard config file.
2. If no mainboard config file exists, then ras-mc-ctl will attempt to read DMI information from the sysfs files
/sys/class/dmi/id/board_vendor
/sys/class/dmi/id/board_name
3. If the sysfs files above do not exist, then ras-mc-ctl will fall back to parsing output of the dmidecode(8) utility. Use of this util-
ity will most often require that ras-mc-ctl be run as root.
SEE ALSO fBrasdaemon(1)RAS-MC-CTL(8)
Check Out this Related Man Page
RAS(9) BSD Kernel Developer's Manual RAS(9)NAME
ras_lookup, ras_fork, ras_purgeall -- restartable atomic sequences
SYNOPSIS
#include <sys/types.h>
#include <sys/proc.h>
#include <sys/ras.h>
void *
ras_lookup(struct proc *p, void *addr);
int
ras_fork(struct proc *p1, struct proc *p2);
int
ras_purgeall(struct proc *p);
DESCRIPTION
Restartable atomic sequences are user code sequences which are guaranteed to execute without preemption. This property is assured by check-
ing the set of restartable atomic sequences registered for a process during cpu_switchto(9). If a process is found to have been preempted
during a restartable sequence, then its execution is rolled-back to the start of the sequence by resetting its program counter saved in its
process control block (PCB).
The RAS functionality is provided by a combination of the machine-independent routines discussed in this page and a machine-dependent compo-
nent in cpu_switchto(9). A port which supports restartable atomic sequences will define __HAVE_RAS in <machine/types.h> for machine-indepen-
dent code to conditionally provide RAS support.
A complicated side-effect of restartable atomic sequences is their interaction with the machine-dependent ptrace(2) support. Specifically,
single-step traps and/or the emulation of single-stepping must carefully consider the effect on restartable atomic sequences. A general
solution is to ignore these traps or disable them within restartable atomic sequences.
FUNCTIONS
The functions which operate on restartable atomic sequences are:
ras_lookup(p, addr)
This function searches the registered restartable atomic sequences for process p which contain the user address addr. If the
address addr is found within a RAS, then the restart address of the RAS is returned, otherwise -1 is returned.
ras_fork(p1, p2)
This function is used to copy all registered restartable atomic sequences for process p1 to process p2. It is primarily called from
fork1(9) when the sequences are inherited from the parent by the child.
ras_purgeall(p)
This function is used to remove all registered restartable atomic sequences for process p. It is primarily used to remove all reg-
istered restartable atomic sequences for a process during exec(3) and by rasctl(2).
CODE REFERENCES
The RAS framework itself is implemented within the file sys/kern/kern_ras.c. Data structures and function prototypes for the framework are
located in <sys/ras.h>. Machine-dependent portions are implemented within cpu_switchto(9) in the machine-dependent file
sys/arch/<arch>/<arch>/locore.S.
SEE ALSO rasctl(2), cpu_switchto(9), fork1(9)
Gregory McGarry, "An Implementation of User-level Restartable Atomic Sequences on the NetBSD Operating System", Proceedings of the FREENIX
Track: 2003 USENIX Annual Technical Conference, USENIX Association,
http://www.usenix.org/publications/library/proceedings/usenix03/tech/freenix03/full_papers/mcgarry/mcgarry.pdf, 311-322, June 9-14, 2003.
HISTORY
The RAS functionality first appeared in NetBSD 2.0.
BSD April 17, 2010 BSD