Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

kmem(4) [ultrix man page]

kmem(4) 						     Kernel Interfaces Manual							   kmem(4)

       kmem - virtual main memory image

       The  special  file is an image of the virtual main memory of the computer.  It may be used, for example, to examine (and even to patch) the
       running system.

       Byte addresses in are interpreted as virtual memory addresses.  For VAXs, the per-process data  for  the  current  process  is  at  virtual
       address 7ffff000(16).

       The memory file is accessed one byte at a time.

See Also


Check Out this Related Man Page

MEM(4)							     Linux Programmer's Manual							    MEM(4)

mem, kmem, port - system memory, kernel memory and system ports DESCRIPTION
mem is a character device file that is an image of the main memory of the computer. It may be used, for example, to examine (and even patch) the system. Byte addresses in mem are interpreted as physical memory addresses. References to nonexistent locations cause errors to be returned. Examining and patching is likely to lead to unexpected results when read-only or write-only bits are present. It is typically created by: mknod -m 660 /dev/mem c 1 1 chown root:kmem /dev/mem The file kmem is the same as mem, except that the kernel virtual memory rather than physical memory is accessed. It is typically created by: mknod -m 640 /dev/kmem c 1 2 chown root:kmem /dev/kmem port is similar to mem, but the I/O ports are accessed. It is typically created by: mknod -m 660 /dev/port c 1 4 chown root:mem /dev/port FILES
/dev/mem /dev/kmem /dev/port SEE ALSO
chown(1), mknod(1), ioperm(2) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at Linux 1992-11-21 MEM(4)
Man Page

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers


Does anybody knows what stands for "kmem_slab" in solaris systems? Im tryng to analise a crash dum and I cannot imagine what that means... thanks HTT (2 Replies)
Discussion started by: htsubamoto
2 Replies

2. Linux

Locking around kmem_cache_destroy

Hi There, I want to make sure that kmem_cache_alloc is not called concurrently with kmem_cache_destroy on module exit and I want be able to use GFP_KERNEL for the kmem_cache_alloc calls. Would a read/write lock be good fro this purpose or is there another method I should be using? Regards,... (0 Replies)
Discussion started by: Brendan Kennedy
0 Replies

3. Solaris

File permission on : kmem file

Hello , I want to check the file permissions of /dev/kmem . I am getting 2 kind of file perms... so which permission i have to consider.. here is 2 case .. 1. ls -al /dev/kmem lrwxrwxrwx 1 root other 27 Sep 8 2008 /dev/kmem -> ../devices/pseudo/mm@0:kmem 2. ... (4 Replies)
Discussion started by: avklinux
4 Replies

4. UNIX for Advanced & Expert Users


hi all, can someone tell what a "kmeminfo" script is all about ? (1 Reply)
Discussion started by: sais
1 Replies

5. Linux

kmemtrace problem

Hi, While building the linux kernel image, I enabled the config option CONFIG_KMEMTRACE. After loaded the image into target, It doesn't have the folder "kmemtrace" inside the /sys/kernel/debug folder. If anyone have the idea, please help me. Thanks & Regards, Manikandan (0 Replies)
Discussion started by: canbumanikandan
0 Replies