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]
Date:	Tue, 31 Oct 2006 07:32:37 -0500
From:	"Richard B. Johnson" <jmodem@...minableFirebug.com>
To:	"Jun Sun" <jsun@...sun.net>, <linux-kernel@...r.kernel.org>
Subject: Re: reserve memory in low physical address - possible?


----- Original Message ----- 
From: "Jun Sun" <jsun@...sun.net>
To: <linux-kernel@...r.kernel.org>
Sent: Tuesday, October 31, 2006 2:22 AM
Subject: reserve memory in low physical address - possible?


>
> This question is specific to i386 architecture.  While I am fairly
> comfortable with Linux kernel, I am not familiar with i386 arch.
>
> My objective is to reserve, or hide from kernel, some memory space in low
> physical address range starting from 0.  The memory amount is in the order
> of 100MB to 200MB.  The total memory is assumed to be around 512MB.
>
> Is this possible?
>
> I understand it is possible to reserve some memory at the end by
> specifying "mem=xxxM" option in kernel command line.  I looked into
> "memmap=xxxM" option but it appears not helpful for what I want.
>

For special purpose (DMA to user-space, etc.), it has become commonplace to 
reserve some high memory.
Then, in your driver, you can find the end of kernel memory as 
(num_physpages * PAGE_SIZE).

You will not be able to reserve any address space starting at 0 anyway, but 
your driver or even
user-space code can memory-map it.

> While searching on the web I also found things like DMA zone and loaders
> etc that all seem to assume the existence low-addressed physical
> memory.  True?
>

Some early (ISA) boards couldn't access address-space beyoond 16 megabytes, 
hense the "low" memory
for DMA.

> I can certainly workaround the loader issue.  I can also re-code the 
> real-mode
> part of kernel code to migrate to higher addresses.  The DMA zone might be
> a thorny one.  Any clues?  Are modern PCs still subject to
> the 16MB DMA zone restriction?
>

Anything that plugs into a PCI bus will __not__ have a low address 
restriction.

> Am I too far off from what I want to do?
>
> Thanks.
>
> Jun
> -
> 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/


-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ