From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/asm changes for v7.1
Date: Mon, 13 Apr 2026 10:53:53 +0200 [thread overview]
Message-ID: <adyvIfxQ5jkmcEvb@gmail.com> (raw)
Linus,
Please pull the latest x86/asm Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-asm-2026-04-13
for you to fetch changes up to 3b19e22cffe61bcdf10ee5e7584cfa3c1c54dc92:
x86/asm updates for v7.1, by Uros Bizjak:
- Remove unnecessary "memory" clobbers from FS/GS base (read-) accessors
- Remove unnecessary "memory" clobber from savesegment()
- Use ASM_INPUT_RM in __loadsegment_fs()
- Implement loadsegment()/savesegment() macros with static inline helpers
- Use savesegment() for segment register reads in ELF core dump
- Use savesegment() in __show_regs() instead of inline asm
- Use correct type for 'gs' variable in __show_regs() to avoid zero-extension
- Clean up 'sel' variable usage in do_set_thread_area()
Thanks,
Ingo
------------------>
Uros Bizjak (8):
x86/asm/fsgsbase: Remove unnecessary "memory" clobbers from FS/GS base (read-) accessors
x86/asm/segment: Remove unnecessary "memory" clobber from savesegment()
x86/asm/segment: Use ASM_INPUT_RM in __loadsegment_fs()
x86/asm/segment: Implement loadsegment()/savesegment() macros with static inline helpers
x86/elf: Use savesegment() for segment register reads in ELF core dump
x86/process/64: Use savesegment() in __show_regs() instead of inline asm
x86/process/32: Use correct type for 'gs' variable in __show_regs() to avoid zero-extension
x86/tls: Clean up 'sel' variable usage in do_set_thread_area()
arch/x86/include/asm/elf.h | 9 +++----
arch/x86/include/asm/fsgsbase.h | 4 +--
arch/x86/include/asm/segment.h | 59 +++++++++++++++++++++++++----------------
arch/x86/kernel/process_32.c | 2 +-
arch/x86/kernel/process_64.c | 8 +++---
arch/x86/kernel/tls.c | 4 ++-
6 files changed, 50 insertions(+), 36 deletions(-)
next reply other threads:[~2026-04-13 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-13 8:53 Ingo Molnar [this message]
2026-04-14 21:45 ` [GIT PULL] x86/asm changes for v7.1 pr-tracker-bot
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=adyvIfxQ5jkmcEvb@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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