search for: non_swap_entry

Displaying 4 results from an estimated 4 matches for "non_swap_entry".

2020 Mar 17
2
[PATCH 3/4] mm: simplify device private page handling in hmm_range_fault
On Tue, Mar 17, 2020 at 09:15:36AM -0300, Jason Gunthorpe wrote: > > Getting rid of HMM_PFN_DEVICE_PRIVATE seems reasonable to me since a driver can > > look at the struct page but what if a driver needs to fault in a page from > > another device's private memory? Should it call handle_mm_fault()? > > Isn't that what this series basically does? > > The
2020 Mar 17
0
[PATCH 3/4] mm: simplify device private page handling in hmm_range_fault
...prefer to see test cases for that first. diff --git a/mm/hmm.c b/mm/hmm.c index b75b3750e03d..2884a3d11a1f 100644 --- a/mm/hmm.c +++ b/mm/hmm.c @@ -276,7 +276,7 @@ static int hmm_vma_handle_pte(struct mm_walk *walk, unsigned long addr, if (!fault && !write_fault) return 0; - if (!non_swap_entry(entry)) + if (!non_swap_entry(entry) || is_device_private_entry(entry)) goto fault; if (is_migration_entry(entry)) {
2020 Mar 17
3
[PATCH 3/4] mm: simplify device private page handling in hmm_range_fault
...s fault to CPU. > diff --git a/mm/hmm.c b/mm/hmm.c > index b75b3750e03d..2884a3d11a1f 100644 > +++ b/mm/hmm.c > @@ -276,7 +276,7 @@ static int hmm_vma_handle_pte(struct mm_walk *walk, unsigned long addr, > if (!fault && !write_fault) > return 0; > > - if (!non_swap_entry(entry)) > + if (!non_swap_entry(entry) || is_device_private_entry(entry)) > goto fault; Yes, OK, makes sense. I've been using v7 of Ralph's tester and it is working well - it has DEVICE_PRIVATE support so I think it can test this flow too. Ralph are you able? This hunk seems...
2020 Oct 08
2
[PATCH] mm: make device private reference counts zero based
ZONE_DEVICE struct pages have an extra reference count that complicates the code for put_page() and several places in the kernel that need to check the reference count to see that a page is not being used (gup, compaction, migration, etc.). Clean up the code so the reference count doesn't need to be treated specially for device private pages, leaving DAX as still being a special case.