MEM(4) Linux Programmer's Manual MEM(4)NAME
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 non-existent 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:mem /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:mem /dev/kmem
Port is similar to mem, but the IO 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)Linux 1992-11-21 MEM(4)
Check Out this Related Man Page
MEM(4) Linux Programmer's Manual MEM(4)NAME
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 http://www.kernel.org/doc/man-pages/.
Linux 1992-11-21 MEM(4)
Does anybody knows what stands for "kmem_slab" in solaris systems? I´m tryng to analise a crash dum and I cannot imagine what that means...
thanks
HTT (2 Replies)
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)
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)
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)