public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat•com>
To: Ingo Molnar <mingo@kernel•org>
Cc: Andrea Arcangeli <aarcange@redhat•com>,
	Thomas Gleixner <tglx@linutronix•de>,
	Stephen Rothwell <sfr@canb•auug.org.au>,
	Andrew Morton <akpm@linux-foundation•org>,
	Ingo Molnar <mingo@elte•hu>,
	"\\\"H. Peter Anvin\\\"" <hpa@zytor•com>,
	Peter Zijlstra <peterz@infradead•org>,
	linux-next@vger•kernel.org, linux-api@vger•kernel.org,
	linux-kernel@vger•kernel.org, Andy Lutomirski <luto@kernel•org>,
	Eric B Munson <emunson@akamai•com>,
	Pavel Emelyanov <xemul@parallels•com>,
	Linus Torvalds <torvalds@linux-foundation•org>,
	Peter Zijlstra <a.p.zijlstra@chello•nl>
Subject: Re: [PATCH] userfaultfd: register syscall numbers for x86 32bit and x86-64 64bit
Date: Fri, 31 Jul 2015 10:13:52 +0100	[thread overview]
Message-ID: <20150731091351.GC2272@work-vm> (raw)
In-Reply-To: <20150731083130.GA24624@gmail.com>

* Ingo Molnar (mingo@kernel•org) wrote:
> 
> * Andrea Arcangeli <aarcange@redhat•com> wrote:
> 
> > This registers the official numbers of the userfaultfd syscall for x86
> > 32bit and x86-64 64bit. This registration allows to ship kernels in
> > production using these two syscall numbers for userfaultfd.
> > 
> > Acked-by: Pavel Emelyanov <xemul@parallels•com>
> > Signed-off-by: Andrea Arcangeli <aarcange@redhat•com>
> > ---
> >  arch/x86/entry/syscalls/syscall_32.tbl | 1 +
> >  arch/x86/entry/syscalls/syscall_64.tbl | 1 +
> >  include/linux/syscalls.h               | 1 +
> >  kernel/sys_ni.c                        | 1 +
> >  4 files changed, 4 insertions(+)
> 
> Hm, is there consensus on the upstream desirability of this sytem call?

I hope so:
   a) It's generic enough that there's interest in using it in
      a range of projects - there's nothing QEMU specific in it.
   b) It's worked very well on the QEMU code that I wrote that uses it
      for postcopy, and has been solid doing that for many months now.
   c) I'm not aware of any suggestions for a different, generic solution
      to solve the same set of problems.
   d) It's got a good self test, that's survived heavy testing.
   e) I think Andrea has addressed all previous comments on it.

Dave

> 
> Thanks,
> 
> 	Ingo
--
Dr. David Alan Gilbert / dgilbert@redhat•com / Manchester, UK

      reply	other threads:[~2015-07-31  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-30 15:34 [PATCH] userfaultfd: register syscall numbers for x86 32bit and x86-64 64bit Andrea Arcangeli
     [not found] ` <1438270467-13324-1-git-send-email-aarcange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-31  8:31   ` Ingo Molnar
2015-07-31  9:13     ` Dr. David Alan Gilbert [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=20150731091351.GC2272@work-vm \
    --to=dgilbert@redhat$(echo .)com \
    --cc=a.p.zijlstra@chello$(echo .)nl \
    --cc=aarcange@redhat$(echo .)com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=emunson@akamai$(echo .)com \
    --cc=hpa@zytor$(echo .)com \
    --cc=linux-api@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=luto@kernel$(echo .)org \
    --cc=mingo@elte$(echo .)hu \
    --cc=mingo@kernel$(echo .)org \
    --cc=peterz@infradead$(echo .)org \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=tglx@linutronix$(echo .)de \
    --cc=torvalds@linux-foundation$(echo .)org \
    --cc=xemul@parallels$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox