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>,
Uros Bizjak <ubizjak@gmail.com>
Subject: [GIT PULL] x86/percpu changes for v6.11
Date: Wed, 17 Jul 2024 16:17:52 +0200 [thread overview]
Message-ID: <ZpfSkENjiIL7HGJV@gmail.com> (raw)
Linus,
Please pull the latest x86/percpu Git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-percpu-2024-07-17
# HEAD: 47ff30cc1be7bf426c03ecc84371452109b416e4 x86/percpu: Enable named address spaces for all capable GCC versions
x86/percpu changes for v6.11:
- Enable the named address spaces based percpu accessors optimization
on all GCC versions that contain this feature, detected through
a build-time testcase. This effectively enables the feature on
GCC 6, GCC 7 and GCC 8 versions.
- Fix operand constraint modifier in __raw_cpu_write()
- Reorganize the per-CPU headers for better readability
- Misc cleanups and fixes
Thanks,
Ingo
------------------>
Ingo Molnar (2):
x86/percpu: Clean up <asm/percpu.h> a bit
x86/percpu: Clean up <asm/percpu.h> vertical alignment details
Uros Bizjak (8):
x86/percpu: Introduce the pcpu_binary_op() macro
x86/percpu: Move some percpu macros around for readability
x86/percpu: Unify percpu read-write accessors
x86/percpu: Introduce the __raw_cpu_read_const() macro
x86/percpu: Fix operand constraint modifier in __raw_cpu_write()
x86/percpu: Rename percpu_stable_op() to __raw_cpu_read_stable()
x86/percpu: Move some percpu accessors around to reduce ifdeffery
x86/percpu: Enable named address spaces for all capable GCC versions
arch/x86/Kconfig | 3 +-
arch/x86/include/asm/percpu.h | 535 ++++++++++++++++++++++--------------------
2 files changed, 281 insertions(+), 257 deletions(-)
next reply other threads:[~2024-07-17 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 14:17 Ingo Molnar [this message]
2024-07-18 23:06 ` [GIT PULL] x86/percpu changes for v6.11 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=ZpfSkENjiIL7HGJV@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=ubizjak@gmail.com \
--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