mis-match in VMALLOC_END value for exynos

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I observed below address limitation changes in below versions of the kernel

linux-3.2: VMALLOC_END=0xF6000000
linux-3.3-rc5: VMALLOC_END=0xFF000000

What is happening is, when I use the SYSMMU to allocate and remap the memory, I need the consistent dma region. Hence I need to call init_consistent_dma_size() to increase the default address range of 2M. Inside this function there is a BUG_ON(base < VMALLOC_END); base is set to the value of CONSISTENT_END(0xffe00000UL) - ALIGN(size, SZ_2M); For any sizes greater than 8M, I generally dont enter the VMALLOC range. But when the consistent DMA size is big, it overlaps with the VMALLOC area.

Can anyone of you please tell me why this change was removed from the exynos files in 3.3 (and above also I think) kernel?

Regards,
Subash
--
To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux SoC Development]     [Linux Rockchip Development]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Linux SCSI]     [Yosemite News]

  Powered by Linux