From: Dave Hansen <dave.hansen@linux.intel.com>
To: Kyle Huey <me@kylehuey.com>, "Robert O'Callahan" <robert@ocallahan.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
Anna Schumaker <Anna.Schumaker@Netapp.com>,
David Howells <dhowells@redhat.com>,
"Dmitry V. Levin" <ldv@altlinux.org>,
Eric B Munson <emunson@akamai.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Jiri Slaby <jslaby@suse.cz>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Borislav Petkov <bp@alien8.de>,
Dmitry Vyukov <dvyukov@google.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] syscalls,x86 Expose arch_prctl on x86-32.
Date: Wed, 14 Sep 2016 14:29:29 -0700 [thread overview]
Message-ID: <57D9C139.1000601@linux.intel.com> (raw)
In-Reply-To: <1473886902-17902-2-git-send-email-khuey@kylehuey.com>
On 09/14/2016 02:01 PM, Kyle Huey wrote:
> Signed-off-by: Kyle Huey <khuey@kylehuey.com>
> ---
> arch/x86/entry/syscalls/syscall_32.tbl | 1 +
> arch/x86/kernel/process.c | 80 ++++++++++++++++++++++++++++++++++
> arch/x86/kernel/process_64.c | 66 ----------------------------
> 3 files changed, 81 insertions(+), 66 deletions(-)
Could you explain a bit about what is going on here? Is it just a plain
old code move, _why_ you had to do it this way, etc...?
next prev parent reply other threads:[~2016-09-14 21:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1473886902-17902-1-git-send-email-khuey@kylehuey.com>
2016-09-14 21:01 ` [PATCH v2 1/3] syscalls,x86 Expose arch_prctl on x86-32 Kyle Huey
2016-09-14 21:29 ` Dave Hansen [this message]
2016-09-14 21:35 ` Kyle Huey
2016-09-14 21:46 ` Dave Hansen
2016-09-14 21:56 ` Kyle Huey
2016-09-14 22:23 ` kbuild test robot
2016-09-15 0:01 ` kbuild test robot
2016-09-15 0:01 ` kbuild test robot
2016-09-15 1:14 ` Andy Lutomirski
2016-09-14 21:01 ` [PATCH v2 2/3] x86 Test and expose CPUID faulting capabilities in /proc/cpuinfo Kyle Huey
2016-09-14 21:35 ` Dave Hansen
2016-09-14 22:03 ` Kyle Huey
2016-09-15 1:17 ` Andy Lutomirski
2016-09-15 2:20 ` Kyle Huey
2016-09-15 20:38 ` H. Peter Anvin
2016-09-15 23:18 ` Andy Lutomirski
2016-09-15 10:07 ` David Vrabel
2016-09-15 10:05 ` [Xen-devel] " David Vrabel
2016-09-15 10:25 ` Jan Beulich
2016-09-15 19:11 ` Kyle Huey
2016-09-15 19:37 ` Andy Lutomirski
2016-09-15 23:36 ` Kyle Huey
2016-09-15 19:41 ` Boris Ostrovsky
2016-09-14 21:01 ` [PATCH v2 3/3] x86,arch_prctl Add ARCH_[GET|SET]_CPUID for controlling the CPUID instruction Kyle Huey
2016-09-15 1:29 ` Andy Lutomirski
2016-09-15 1:47 ` Kyle Huey
2016-09-15 1:54 ` Andy Lutomirski
2016-09-15 2:19 ` Kyle Huey
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=57D9C139.1000601@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=Anna.Schumaker@Netapp.com \
--cc=aryabinin@virtuozzo.com \
--cc=bp@alien8.de \
--cc=dhowells@redhat.com \
--cc=dvyukov@google.com \
--cc=emunson@akamai.com \
--cc=hpa@zytor.com \
--cc=jslaby@suse.cz \
--cc=ldv@altlinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=me@kylehuey.com \
--cc=mingo@redhat.com \
--cc=mst@redhat.com \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=robert@ocallahan.org \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox