*** UNIX MANUAL PAGE BROWSER ***

A Nergahak database for man pages research.

Navigation

Directory Browser

1Browse 4.4BSD4.4BSD
1Browse Digital UNIXDigital UNIX 4.0e
1Browse FreeBSDFreeBSD 14.3
1Browse MINIXMINIX 3.4.0rc6-d5e4fc0
1Browse NetBSDNetBSD 10.1
1Browse OpenBSDOpenBSD 7.7
1Browse UNIX v7Version 7 UNIX
1Browse UNIX v10Version 10 UNIX

Manual Page Search

Manual Page Result

0 Command: mem | Section: 4 | Source: UNIX v10 | File: mem.4
MEM(4) Kernel Interfaces Manual MEM(4) NAME mem, kmem, kUmem, mtpr, fineclock - memory and VAX processor registers DESCRIPTION Mem is a file that is an image of the main memory of the computer. It may be used to examine (and even to patch) the system. Byte addresses in mem are interpreted as physical memory addresses. References to non-existent locations return errors. Kmem and kUmem are like mem, but access kernel-mode virtual memory. KUmem promises that reads and writes will be done in two-byte quanti- ties; this is convenient for UNIBUS accesses. Mtpr accesses VAX internal processor registers. Each register is 4 bytes long; register n may be read or written at address n*4. Fineclock reads a high-resolution clock. Reading four bytes returns a 32-bit unsigned integer representing the number of microseconds since the epoch 00:00:00 GMT, Jan. 1, 1970, with high-order bits discarded. Mem, kmem, kUmem, and mtpr have minor device numbers 0, 1, 3, and 5. Fineclock is a separate driver; the minor device number is ignored. FILES SEE ALSO time(2) VAX Hardware Handbook BUGS Examining and patching device and processor registers may give unex- pected results when read-only or write-only bits are present. An attempt to read a nonexistent processor register returns 0 instead of an error. The fineclock counter overflows every hour or so. It is only as pre- cise as the hardware; hence it is inaccurate on a MicroVAX. MEM(4)

Navigation Options