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.10
Date: Mon, 13 May 2024 09:57:04 +0200 [thread overview]
Message-ID: <ZkHH0E9XmbUSEzA6@gmail.com> (raw)
In-Reply-To: <ZkHFtnfjXcZQX5ds@gmail.com>
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-05-13
# HEAD: 93cfa544cf9e4771def159002304a2e366cd97af x86/percpu: Introduce raw_cpu_read_long() to reduce ifdeffery
x86/percpu changes for v6.10:
- Expand the named address spaces optimizations down to
GCC 9.1+.
- Re-enable named address spaces with sanitizers for GCC 13.3+
- Generate better this_percpu_xchg_op() code
- Introduce raw_cpu_read_long() to reduce ifdeffery
- Simplify the x86_this_cpu_test_bit() et al macros
- Address Sparse warnings
- Misc cleanups & fixes
Thanks,
Ingo
------------------>
Uros Bizjak (11):
x86/percpu: Convert this_percpu_xchg_op() from asm() to C code, to generate better code
x86/percpu: Move raw_percpu_xchg_op() to a better place
x86/percpu: Re-enable named address spaces with KASAN for GCC 13.3+
x86/percpu: Enable named address spaces for GCC 9.1+
x86/percpu: Unify arch_raw_cpu_ptr() defines
x86/percpu: Do not use this_cpu_read_stable_8() for 32-bit targets
x86/percpu: Use __force to cast from __percpu address space
x86/percpu: Re-enable named address spaces with sanitizers for GCC 13.3+
x86/percpu: Fix x86_this_cpu_variable_test_bit() asm template
x86/percpu: Rewrite x86_this_cpu_test_bit() and friends as macros
x86/percpu: Introduce raw_cpu_read_long() to reduce ifdeffery
arch/um/include/asm/cpufeature.h | 3 +-
arch/x86/Kconfig | 14 ++--
arch/x86/include/asm/cpufeature.h | 3 +-
arch/x86/include/asm/percpu.h | 157 +++++++++++++++++---------------------
4 files changed, 78 insertions(+), 99 deletions(-)
next prev parent reply other threads:[~2024-05-13 7:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 7:48 [GIT PULL] x86/mm changes for v6.10 Ingo Molnar
2024-05-13 7:57 ` Ingo Molnar [this message]
2024-05-14 2:51 ` [GIT PULL] x86/percpu " pr-tracker-bot
2024-05-14 2:51 ` [GIT PULL] x86/mm " 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=ZkHH0E9XmbUSEzA6@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