linux-kernel - Re: Reading a physical memory location

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1a297b360707110150x56e8ad6cu64ab768e7d3ce6ed@mail.gmail.com>
Date:	Wed, 11 Jul 2007 12:50:20 +0400
From:	"Manu Abraham" <abraham.manu@...il.com>
To:	"Nobin Mathew" <nobin.mathew@...il.com>
Cc:	"vraghavan3@...l.gatech.edu" <vraghavan3@...l.gatech.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: Reading a physical memory location

On 7/11/07, Nobin Mathew <nobin.mathew@...il.com> wrote:
> See this in the documentation
>
> The returned virtual address is a current CPU mapping for the memory
> address given. It is only valid to use this function on addresses that
> have a kernel mapping
>
> This function does not handle bus mappings for DMA transfers. In
> almost all conceivable cases a device driver should not be using this
> function
>

To get a better idea, look here
http://tldp.org/LDP/khg/HyperNews/get/devices/addrxlate.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/