Re: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT

* Heiko Carstens <[email protected]> wrote:

> From: Heiko Carstens <[email protected]>
> 
> __alloc_bootmem_low() and __alloc_bootmem_low_node() should use 
> MAX_DMA_ADDRESS as limit which is per architecture instead of a global 
> LOW32LIMIT. Otherwise the bootmem allocator may return addresses to 
> memory regions which cannot be used for DMA access.

> -#define LOW32LIMIT 0xffffffff

>  		if ((ptr = __alloc_bootmem_core(bdata, size,
> -						 align, goal, LOW32LIMIT)))
> +						 align, goal, MAX_DMA_ADDRESS)))

but this limits things to 16MB on i686. Are you sure this wont break 
anything?

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT
    • From: Martin Schwidefsky <[email protected]>

• References:
  • [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT
    • From: Heiko Carstens <[email protected]>

• Prev by Date: Re: Sound problems with snd_hda on x86_64
• Next by Date: Re: Bad ext3/nfs DoS bug
• Previous by thread: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT
• Next by thread: Re: [patch] bootmem: use MAX_DMA_ADDRESS instead of LOW32LIMIT
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]