From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: [question] What's the difference between /dev/kmem and /dev/mem
Date: Thu, 11 Aug 2005 17:36:28 -0400 [thread overview]
Message-ID: <1123796188.17269.127.camel@localhost.localdomain> (raw)
OK, I thought I use to know this. But what is the difference
between /dev/kmem and /dev/mem. I thought that with /dev/kmem you could
use the actual kernel addresses to read from.
For example, if I wanted to read the current variable X in the kernel, I
could look up the address of X in System.map, then mmaping to /dev/kmem
I could get to that variable using the address that I got from
System.map. But this doesn't seem to work.
I'm getting an IO error on read. And looking at this I see:
static int mmap_kmem(struct file * file, struct vm_area_struct * vma)
{
unsigned long long val;
/*
* RED-PEN: on some architectures there is more mapped memory
* than available in mem_map which pfn_valid checks
* for. Perhaps should add a new macro here.
*
* RED-PEN: vmalloc is not supported right now.
*/
if (!pfn_valid(vma->vm_pgoff))
return -EIO;
val = (u64)vma->vm_pgoff << PAGE_SHIFT;
vma->vm_pgoff = __pa(val) >> PAGE_SHIFT;
return mmap_mem(file, vma);
}
I printed out the value in vma->vm_pgoff, and it still has the
0xc0000000 (but shifted >> 12). Isn't this suppose to also remove the
0xc? Or am I just totally off here?
Thanks,
-- Steve
next reply other threads:[~2005-08-11 21:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 21:36 Steven Rostedt [this message]
2005-08-12 1:15 ` [PATCH] Fix mmap_kmem (was: [question] What's the difference between /dev/kmem and /dev/mem) Steven Rostedt
2005-08-12 14:25 ` Hugh Dickins
2005-08-12 16:35 ` Linus Torvalds
2005-08-12 16:56 ` Dave Jones
2005-08-12 17:07 ` Steven Rostedt
2005-08-12 17:16 ` Arjan van de Ven
2005-08-12 17:32 ` Steven Rostedt
2005-08-12 17:01 ` Steven Rostedt
2005-08-13 13:39 ` [PATCH] Fix mmap kmem " Nicolas George
2005-08-13 16:50 ` [PATCH] Fix mmap_kmem " Arjan van de Ven
2005-08-13 16:56 ` Linus Torvalds
2005-08-13 17:25 ` Arjan van de Ven
2005-08-13 17:37 ` Linus Torvalds
2005-08-13 18:18 ` Arjan van de Ven
2005-08-16 22:12 ` Greg Edwards
2005-08-16 23:33 ` Alan Cox
2005-08-16 23:47 ` Steven Rostedt
2005-08-15 19:33 ` Olaf Hering
2005-08-15 21:14 ` Jeff Dike
2005-08-15 21:50 ` Olaf Hering
2005-08-15 22:41 ` Linus Torvalds
2005-08-16 1:16 ` Steven Rostedt
2005-08-16 1:22 ` Steven Rostedt
2005-08-16 1:36 ` Linus Torvalds
2005-08-13 16:57 ` Joshua Hudson
2005-08-13 17:27 ` Arjan van de Ven
2005-08-14 14:50 ` Martin J. Bligh
2005-08-18 14:07 ` Arjan van de Ven
2005-08-18 14:18 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1123796188.17269.127.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox