From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/asm changes for v4.20
Date: Tue, 23 Oct 2018 13:15:01 +0200 [thread overview]
Message-ID: <20181023111501.GA114423@gmail.com> (raw)
Linus,
Please pull the latest x86-asm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-asm-for-linus
# HEAD: ec3a94188df7d28b374868d9a2a0face910e62ab x86/fsgsbase/64: Clean up various details
The main changes in this cycle were the fsgsbase related preparatory
patches from Chang S. Bae - but there's also an optimized
memcpy_flushcache() and a cleanup for the __cmpxchg_double() assembly
glue.
Thanks,
Ingo
------------------>
Andy Lutomirski (1):
x86/fsgsbase/64: Fix ptrace() to read the FS/GS base accurately
Chang S. Bae (7):
x86/fsgsbase/64: Introduce FS/GS base helper functions
x86/fsgsbase/64: Make ptrace use the new FS/GS base helpers
x86/fsgsbase/64: Convert the ELF core dump code to the new FSGSBASE helpers
x86/fsgsbase/64: Factor out FS/GS segment loading from __switch_to()
x86/segments/64: Rename the GDT PER_CPU entry to CPU_NUMBER
x86/vdso: Introduce helper functions for CPU and node number
x86/vdso: Initialize the CPU/node NR segment descriptor earlier
Ingo Molnar (2):
x86/segments: Introduce the 'CPUNODE' naming to better document the segment limit CPU/node NR trick
x86/fsgsbase/64: Clean up various details
Mikulas Patocka (1):
x86/asm: Optimize memcpy_flushcache()
Uros Bizjak (1):
x86/asm: Use CC_SET()/CC_OUT() in __cmpxchg_double()
arch/x86/entry/vdso/vgetcpu.c | 8 +-
arch/x86/entry/vdso/vma.c | 38 +-------
arch/x86/include/asm/cmpxchg.h | 10 ++-
arch/x86/include/asm/elf.h | 6 +-
arch/x86/include/asm/fsgsbase.h | 49 +++++++++++
arch/x86/include/asm/segment.h | 46 +++++++++-
arch/x86/include/asm/string_64.h | 20 ++++-
arch/x86/include/asm/vgtod.h | 26 ------
arch/x86/kernel/cpu/common.c | 24 +++++
arch/x86/kernel/process_64.c | 183 ++++++++++++++++++++++++++++++---------
arch/x86/kernel/ptrace.c | 28 ++----
arch/x86/lib/usercopy_64.c | 4 +-
12 files changed, 299 insertions(+), 143 deletions(-)
create mode 100644 arch/x86/include/asm/fsgsbase.h
reply other threads:[~2018-10-23 11:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20181023111501.GA114423@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.