All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Andrea Arcangeli <aarcange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: "Michael Kerrisk (man-pages)"
	<mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-man <linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] New page describing userfaultfd(2) system call.
Date: Thu, 29 Dec 2016 09:02:34 +0200	[thread overview]
Message-ID: <20161229070233.GA9996@rapoport-lnx> (raw)
In-Reply-To: <20161227112038.GD16976-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Hello,

On Tue, Dec 27, 2016 at 12:20:38PM +0100, Andrea Arcangeli wrote:
> Hello,
> 
> On Tue, Dec 27, 2016 at 09:16:25AM +0100, Michael Kerrisk (man-pages) wrote:
> > Hi Mike,
> > 
> > Thanks for working on this page. Just for background (since it helps
> > me fore review), how did you get the info that is documented in the
> > page?
> 
> Mike maintained and contributed to the non-cooperative support of
> userfaultfd (not documented yet in the manpage because not upstream
> yet) and he also wrote from scratch the shmem support of userfaultfd
> (also still queued for upstream merging). So I assume all information
> in the manpage has been obtained by reading the kernel code of
> userfaultfd.

Andrea, thanks for the nice summary :)
I'm working on post-copy migration in CRIU, so except reading the kernel
code, a had quite a few chances to experiment with userfaultfd :)
 
> Thanks,
> Andrea
>

--
Sincerely yours,
Mike. 

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2016-12-29  7:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21  8:08 [PATCH] New page describing userfaultfd(2) system call Mike Rapoport
     [not found] ` <1482307713-21853-1-git-send-email-rppt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2016-12-27  8:14   ` Michael Kerrisk (man-pages)
2016-12-27  8:16   ` Michael Kerrisk (man-pages)
     [not found]     ` <CAKgNAkgb=qfTZA4fzUGVmLis-bK5kFU0PfYwHs4dhz+1RRa2TQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-27 11:20       ` Andrea Arcangeli
     [not found]         ` <20161227112038.GD16976-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-12-29  7:02           ` Mike Rapoport [this message]
2016-12-27 11:16   ` Andrea Arcangeli

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=20161229070233.GA9996@rapoport-lnx \
    --to=rppt-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=aarcange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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.