* mis-match in VMALLOC_END value for exynos
@ 2012-03-30 6:23 Subash Patel
0 siblings, 0 replies; only message in thread
From: Subash Patel @ 2012-03-30 6:23 UTC (permalink / raw)
To: linux-samsung-soc
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-03-30 6:23 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-30 6:23 mis-match in VMALLOC_END value for exynos Subash Patel
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.