Lines Matching refs:page

1 page owner: Tracking about who allocated each page
6 page owner is for the tracking about who allocated each page.
9 and order of pages is stored into certain storage for each page.
13 Although we already have tracepoint for tracing page allocation/free,
14 using it for analyzing who allocate each page is rather complex. We need
20 page owner can also be used for various purposes. For example, accurate
22 each page. It is already implemented and activated if page owner is
25 page owner is disabled in default. So, if you'd like to use it, you need
27 with page owner and page owner is disabled in runtime due to no enabling
30 memory overhead. And, page owner inserts just two unlikely branches into
31 the page allocator hotpath and if it returns false then allocation is
32 done like as the kernel without page owner. These two unlikely branches
36 - Without page owner
40 - With page owner
48 page owner and turning it on if needed would be great option to debug
51 There is one notice that is caused by implementation detail. page owner
52 stores information into the memory from struct page extension. This memory
53 is initialized some time later than that page allocator starts in sparse
58 at least, we can tell whether the page is allocated or not,
61 page extension feature. Anyway, after that, no page is left in
70 2) Enable page owner
75 4) Analyze information from page owner
80 	See the result about who allocated each page