public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: vraghavan3@mail.gatech.edu
Cc: Nobin Mathew <nobin.mathew@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Reading a physical memory location
Date: Tue, 24 Jul 2007 14:48:44 +0200	[thread overview]
Message-ID: <46A5F52C.6060101@aitel.hist.no> (raw)
In-Reply-To: <1184091142.4693cc06850f7@webmail.mail.gatech.edu>

vraghavan3@mail.gatech.edu wrote:
> Thanks for the quick reply. But I was wondering as to why I would have to map
> the physical address to the virtual address when I know that the string is
> permanently in the physical memory because its loaded into flash. 
Because that is how any CPU with a MMU works.
All accesses to memory goes through page tables (virtual memory) -
there is no alternative. But this is not a problem, as the kernel can
map any physical address for you. 

> Is there a way
> to directly read from the physical memory location? 
The way is to map the page containing that address.  You can
then read whatever you want from that page. Nothing is ever accessed
by physical address, physical addresses is only used indirectly
to set up the page tables.

Helge Hafting

      parent reply	other threads:[~2007-07-24 13:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 19:47 Reading a physical memory location vraghavan3
2007-07-09 22:39 ` Nobin Mathew
2007-07-10 18:12   ` vraghavan3
2007-07-10 22:02     ` Manu Abraham
2007-07-11  5:43       ` Nobin Mathew
2007-07-11  8:11         ` Manu Abraham
2007-07-11  8:14           ` Nobin Mathew
2007-07-11  8:50             ` Manu Abraham
2007-07-11  8:57               ` Nobin Mathew
2007-07-11 10:00               ` Clemens Koller
2007-07-24 12:48     ` Helge Hafting [this message]

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=46A5F52C.6060101@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nobin.mathew@gmail.com \
    --cc=vraghavan3@mail.gatech.edu \
    /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