From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, arnd@arndb.de,
Al Viro <viro@zeniv.linux.org.uk>,
Mel Gorman <mgorman@techsingularity.net>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 0/9] [v3] System Calls for Memory Protection Keys
Date: Thu, 30 Jun 2016 11:41:23 +0200 [thread overview]
Message-ID: <20160630094123.GA29268@gmail.com> (raw)
In-Reply-To: <20160609000117.71AC7623@viggo.jf.intel.com>
* Dave Hansen <dave@sr71.net> wrote:
> Are there any concerns with merging these into the x86 tree so
> that they go upstream for 4.8? The updates here are pretty
> minor.
> include/linux/pkeys.h | 39 +-
> include/uapi/asm-generic/mman-common.h | 5 +
> include/uapi/asm-generic/unistd.h | 12 +-
> mm/mprotect.c | 134 +-
So I'd love to have some high level MM review & ack for these syscall ABI
extensions.
Thanks,
Ingo
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Dave Hansen <dave@sr71.net>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-api@vger.kernel.org, linux-arch@vger.kernel.org,
linux-mm@kvack.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, arnd@arndb.de,
Al Viro <viro@zeniv.linux.org.uk>,
Mel Gorman <mgorman@techsingularity.net>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 0/9] [v3] System Calls for Memory Protection Keys
Date: Thu, 30 Jun 2016 11:41:23 +0200 [thread overview]
Message-ID: <20160630094123.GA29268@gmail.com> (raw)
Message-ID: <20160630094123.gGjyekU2vIggeQSIgcTxbtjxc-Ymbn840jkRcAc2U8s@z> (raw)
In-Reply-To: <20160609000117.71AC7623@viggo.jf.intel.com>
* Dave Hansen <dave@sr71.net> wrote:
> Are there any concerns with merging these into the x86 tree so
> that they go upstream for 4.8? The updates here are pretty
> minor.
> include/linux/pkeys.h | 39 +-
> include/uapi/asm-generic/mman-common.h | 5 +
> include/uapi/asm-generic/unistd.h | 12 +-
> mm/mprotect.c | 134 +-
So I'd love to have some high level MM review & ack for these syscall ABI
extensions.
Thanks,
Ingo
next prev parent reply other threads:[~2016-06-30 9:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 0:01 [PATCH 0/9] [v3] System Calls for Memory Protection Keys Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 2/9] mm: implement new pkey_mprotect() system call Dave Hansen
2016-06-09 0:01 ` Dave Hansen
[not found] ` <20160609000120.A3DD5140-LXbPSdftPKxrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-11 9:47 ` Thomas Gleixner
2016-06-11 9:47 ` Thomas Gleixner
2016-06-13 16:03 ` Dave Hansen
2016-06-13 16:03 ` Dave Hansen
2016-06-13 16:03 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 3/9] x86, pkeys: make mprotect_key() mask off additional vm_flags Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 4/9] x86: wire up mprotect_key() system call Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 5/9] x86, pkeys: allocation/free syscalls Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 6/9] x86, pkeys: add pkey set/get syscalls Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 7/9] generic syscalls: wire up memory protection keys syscalls Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` [PATCH 8/9] pkeys: add details of system call use to Documentation/ Dave Hansen
2016-06-09 0:01 ` Dave Hansen
[not found] ` <20160609000117.71AC7623-LXbPSdftPKxrdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2016-06-09 0:01 ` [PATCH 9/9] x86, pkeys: add self-tests Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-09 0:01 ` Dave Hansen
2016-06-30 9:41 ` Ingo Molnar [this message]
2016-06-30 9:41 ` [PATCH 0/9] [v3] System Calls for Memory Protection Keys Ingo Molnar
[not found] ` <20160630094123.GA29268-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-06-30 16:46 ` Dave Hansen
2016-06-30 16:46 ` Dave Hansen
2016-06-30 16:46 ` Dave Hansen
2016-06-30 17:40 ` Andy Lutomirski
2016-06-30 17:40 ` Andy Lutomirski
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=20160630094123.GA29268@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=dave@sr71.net \
--cc=hughd@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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.