linux-kernel - Re: read physical address space

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] [day] [month] [year] [list]

Message-ID: <CAHBu3sgb3fFpieEbGupdTmK4c18XaNXBjYarnZJcPMqLHh4CNw@mail.gmail.com>
Date:	Tue, 24 Nov 2015 15:48:24 +0000
From:	alan hopes <hopes.alan@...il.com>
To:	yalin wang <yalin.wang2010@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: read physical address space

Thanks Yalin.

Yeah, got it.. So, it means I can't directly access physical address,
its only the responsibility of MMU to access it. Even if I have a
physical address, I need to convert it to kernel virtual address to
access it to maintain consistency with other general user-mode memory
access operation.

Thanks
Alan.

On Tue, Nov 17, 2015 at 4:28 PM, yalin wang <yalin.wang2010@...il.com> wrote:
> you should access it like this:
>         printk ( *(int*)kmap(pays_to_page(pays_addr)));
>
> pays address must be mapped into virtual address before access it .
>> On Nov 17, 2015, at 23:21, alan hopes <hopes.alan@...il.com> wrote:
>>
>> phys_addr
>
--
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/