Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1571225 > unrolled thread

Re: [PATCH v2 2/5] userfaultfd: non-cooperative: add event for memory unmaps

Started byAndrew Morton <akpm@linux-foundation.org>
First post2017-02-01 01:50 +0100
Last post2017-02-01 07:40 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v2 2/5] userfaultfd: non-cooperative: add event for  memory unmaps Andrew Morton <akpm@linux-foundation.org> - 2017-02-01 01:50 +0100
    Re: [PATCH v2 2/5] userfaultfd: non-cooperative: add event for  memory unmaps Mike Rapoport <rppt@linux.vnet.ibm.com> - 2017-02-01 07:40 +0100

#1571225 — Re: [PATCH v2 2/5] userfaultfd: non-cooperative: add event for memory unmaps

FromAndrew Morton <akpm@linux-foundation.org>
Date2017-02-01 01:50 +0100
SubjectRe: [PATCH v2 2/5] userfaultfd: non-cooperative: add event for memory unmaps
Message-ID<t5Rhw-7s5-5@gated-at.bofh.it>
On Fri, 27 Jan 2017 20:44:30 +0200 Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:

> When a non-cooperative userfaultfd monitor copies pages in the background,
> it may encounter regions that were already unmapped. Addition of
> UFFD_EVENT_UNMAP allows the uffd monitor to track precisely changes in the
> virtual memory layout.
> 
> Since there might be different uffd contexts for the affected VMAs, we
> first should create a temporary representation for the unmap event for each
> uffd context and then notify them one by one to the appropriate userfault
> file descriptors.
> 
> The event notification occurs after the mmap_sem has been released.

I was going to bug you about not updating
Documentation/vm/userfaultfd.txt but the UFFD_FEATURE flags aren't
documented?

[toc] | [next] | [standalone]


#1571280

FromMike Rapoport <rppt@linux.vnet.ibm.com>
Date2017-02-01 07:40 +0100
Message-ID<t5WKd-2n7-5@gated-at.bofh.it>
In reply to#1571225
On Tue, Jan 31, 2017 at 04:39:28PM -0800, Andrew Morton wrote:
> On Fri, 27 Jan 2017 20:44:30 +0200 Mike Rapoport <rppt@linux.vnet.ibm.com> wrote:
> 
> > When a non-cooperative userfaultfd monitor copies pages in the background,
> > it may encounter regions that were already unmapped. Addition of
> > UFFD_EVENT_UNMAP allows the uffd monitor to track precisely changes in the
> > virtual memory layout.
> > 
> > Since there might be different uffd contexts for the affected VMAs, we
> > first should create a temporary representation for the unmap event for each
> > uffd context and then notify them one by one to the appropriate userfault
> > file descriptors.
> > 
> > The event notification occurs after the mmap_sem has been released.
> 
> I was going to bug you about not updating
> Documentation/vm/userfaultfd.txt but the UFFD_FEATURE flags aren't
> documented?
 
I'm going to send the documentation update in the next few days.

--
Sincerely yours,
Mike.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web