All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Pavel Emelyanov <xemul@virtuozzo.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	"Kirill A. Shutemov" <kirill@shutemov.name>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, Mike Rapoport <mike.rapoport@gmail.com>
Subject: Re: [PATCH 0/1] soft_dirty: fix soft_dirty during THP split
Date: Tue, 23 Aug 2016 14:03:26 +0300	[thread overview]
Message-ID: <20160823110325.GD1205@rapoport-lnx> (raw)
In-Reply-To: <57B70F33.9090902@virtuozzo.com>

On Fri, Aug 19, 2016 at 04:52:51PM +0300, Pavel Emelyanov wrote:
> On 08/19/2016 04:43 PM, Andrea Arcangeli wrote:
> > On Fri, Aug 19, 2016 at 04:20:22PM +0300, Pavel Emelyanov wrote:
> >> And (!) after non-cooperative patches are functional too.
> > 
> > I merged your non-cooperative patches in my tree although there's no
> > testcase to exercise them yet.
> 
> Hm... Are you talking about some in-kernel test, or just any? We have
> tests in CRIU tree for UFFD (not sure we've wired up the non-cooperative
> part though).

Well, CRIU is by definition non-cooperative :)
Still, we don't have fork() and other events in CRIU lazy restore yet.
I have some brute force additions to the selftests/vm/userfaultfd.c that
verify that the events work, and I'm trying now to get a clean version.

BTW, with addition of hugetlbfs and tmpfs support to userfaultfd, we'd need
MADV_REMOVE and fallocate(PUNCH_HOLE) events in addition to
MADV_DONTNEED...
 
> > 
> > Thanks,
> > Andrea
> > .
> > 
> 
> -- Pavel
> 
--
Sincerely yours,
Mike.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      parent reply	other threads:[~2016-08-23 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 12:41 [PATCH 0/1] soft_dirty: fix soft_dirty during THP split Andrea Arcangeli
2016-08-19 12:41 ` [PATCH 1/1] " Andrea Arcangeli
2016-08-19 13:17   ` Pavel Emelyanov
2016-08-19 13:20 ` [PATCH 0/1] " Pavel Emelyanov
2016-08-19 13:43   ` Andrea Arcangeli
2016-08-19 13:52     ` Pavel Emelyanov
2016-08-19 14:37       ` Andrea Arcangeli
2016-08-22 16:35         ` Pavel Emelyanov
2016-08-23 11:03       ` Mike Rapoport [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160823110325.GD1205@rapoport-lnx \
    --to=rppt@linux.vnet.ibm.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.org \
    --cc=mike.rapoport@gmail.com \
    --cc=xemul@virtuozzo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.