Hello, On 2/5/2013 9:28 AM, Mel Gorman wrote:
On Tue, Feb 05, 2013 at 08:29:26AM +0900, Kyungmin Park wrote: > > > > (This information is needed so that others can make patch-scheduling > > decisions and should be included in all bugfix changelogs unless it is > > obvious). > > CMA Highmem support is new feature. so don't need to go stable tree. > You could have given a lot more information to that question! How new a feature is it?
ARM DMA-mapping, the only in-kernel client of CMA, will gain himem support in
v3.9. On the other hand, there might be out of tree clients of alloc_contig_migrate_range()/dma_alloc_from_contiguous() API. If you think we should care about them, then this patch might need to be backported to stable kernels.
Does this mean that this patch must go in before 3.8 releases or is it a fix against a patch that is only in Andrew's tree? If the patch is only in Andrew's tree, which one is it and should this be folded in as a fix? On a semi-related note; is there a plan for backporting highmem support for the LTSI kernel considering it's aimed at embedded and CMA was highlighted in their announcment for 3.4 support?
I've just noticed recently that LTSI released v3.4 kernel with CMA support. I've checked that code only briefly and noticed that it didn't have all the CMA related patches which are available in v3.8-rc1. I will take a look at that code and maybe I will find some time to backport some more patches from mainline, but please note that mainline kernel has higher priority. Best regards -- Marek Szyprowski Samsung Poland R&D Center -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>