Re: [PATCH] kvm: Faults which trigger IO release the mmap_sem
From: Paolo Bonzini
Date: Tue Sep 16 2014 - 14:30:10 EST
Il 16/09/2014 18:52, Andres Lagar-Cavilla ha scritto:
> Was this:
> npages = get_user_pages(NULL, mm, addr, 1, 1, 0, NULL, NULL);
> the intention rather than get_user_pages_fast?
I meant the intention of the original author, not yours.
> By that point in the call chain I felt comfortable dropping the _fast.
> All paths that get there have already tried _fast (and some have tried
> I think a first patch should introduce kvm_get_user_page_retry ("Retry a
> fault after a gup with FOLL_NOWAIT.") and the second would add
> FOLL_TRIED ("This properly relinquishes mmap semaphore if the
> filemap/swap has to wait on page lock (and retries the gup to completion
> after that").
> That's not what FOLL_TRIED does. The relinquishing of mmap semaphore is
> done by this patch minus the FOLL_TRIED bits. FOLL_TRIED will let the
> fault handler (e.g. filemap) know that we've been there and waited on
> the IO already, so in the common case we won't need to redo the IO.
Yes, that's not what FOLL_TRIED does. But it's the difference between
get_user_pages and kvm_get_user_page_retry, right?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/