Displaying 2 results from an estimated 2 matches for "compound_page".
2020 Jun 22
1
[PATCH 09/16] mm/hmm: add output flag for compound page mapping
...lag says the CPU is mapping the whole compound page (based on compound_order)
> and that the caller can use device mappings up to the size of compound_order(page).
No, I got it, I just don't like the assumption that just because a PMD
or PUD points to a page that the only possible value for
compound_page() is PMD or PUD respectively. Partial mapping should be
possible in both cases, if not today, then maybe down the road with
some of the large page work that has been floating about
It seems much safer to just directly encode the PUD/PMD size in the
flags
Jason
2020 Jun 22
2
[PATCH 09/16] mm/hmm: add output flag for compound page mapping
On Fri, Jun 19, 2020 at 02:56:42PM -0700, Ralph Campbell wrote:
> hmm_range_fault() returns an array of page frame numbers and flags for
> how the pages are mapped in the requested process' page tables. The PFN
> can be used to get the struct page with hmm_pfn_to_page() and the page size
> order can be determined with compound_order(page) but if the page is larger
> than order 0