Re: [PATCH 3/3] mm/cma: always check which page cause allocation failure

On Tue, Nov 24, 2015 at 04:27:56PM +0100, Vlastimil Babka wrote: > On 11/13/2015 03:23 AM, Joonsoo Kim wrote: > >Now, we have tracepoint in test_pages_isolated() to notify > >pfn which cannot be isolated. But, in alloc_contig_range(), > >some error path doesn't call test_pages_isolated() so it's st

Re: [PATCH 3/3] mm/cma: always check which page cause allocation failure

On 11/13/2015 03:23 AM, Joonsoo Kim wrote: Now, we have tracepoint in test_pages_isolated() to notify pfn which cannot be isolated. But, in alloc_contig_range(), some error path doesn't call test_pages_isolated() so it's still hard to know exact pfn that causes allocation failure. This patch cha

[PATCH 3/3] mm/cma: always check which page cause allocation failure

Now, we have tracepoint in test_pages_isolated() to notify pfn which cannot be isolated. But, in alloc_contig_range(), some error path doesn't call test_pages_isolated() so it's still hard to know exact pfn that causes allocation failure. This patch change this situation by calling test_pages_isol

[PATCH 3/3] mm/cma: always check which page cause allocation failure

Now, we have tracepoint in test_pages_isolated() to notify pfn which cannot be isolated. But, in alloc_contig_range(), some error path doesn't call test_pages_isolated() so it's still hard to know exact pfn that causes allocation failure. This patch change this situation by calling test_pages_isol