lkml.org 
[lkml]   [2021]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [PATCH mm,percpu_ref,rcu 3/6] mm: Make mem_dump_obj() handle vmalloc() memory
    From
    Date
    On 1/6/21 2:17 AM, paulmck@kernel.org wrote:
    > From: "Paul E. McKenney" <paulmck@kernel.org>
    >
    > This commit adds vmalloc() support to mem_dump_obj(). Note that the
    > vmalloc_dump_obj() function combines the checking and dumping, in
    > contrast with the split between kmem_valid_obj() and kmem_dump_obj().
    > The reason for the difference is that the checking in the vmalloc()
    > case involves acquiring a global lock, and redundant acquisitions of
    > global locks should be avoided, even on not-so-fast paths.
    >
    > Note that this change causes on-stack variables to be reported as
    > vmalloc() storage from kernel_clone() or similar, depending on the degree
    > of inlining that your compiler does. This is likely more helpful than
    > the earlier "non-paged (local) memory".
    >
    > Cc: Andrew Morton <akpm@linux-foundation.org>
    > Cc: Joonsoo Kim <iamjoonsoo.kim@lge.com>
    > Cc: <linux-mm@kvack.org>
    > Reported-by: Andrii Nakryiko <andrii@kernel.org>
    > Signed-off-by: Paul E. McKenney <paulmck@kernel.org>

    Acked-by: Vlastimil Babka <vbabka@suse.cz>

    \
     
     \ /
      Last update: 2021-01-08 16:33    [W:4.367 / U:0.372 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site