From: Dave Hansen <dave.hansen@linux.intel.com>
To: torvalds@linux-foundation.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [GIT PULL] x86/misc for 7.0-rc1
Date: Mon, 9 Feb 2026 13:10:03 -0800 [thread overview]
Message-ID: <20260209211003.2330804-1-dave.hansen@linux.intel.com> (raw)
Hi Linus,
Please pull the usual smattering of x86/misc changes for 7.0-rc1.
The IPv6 patch in here surprised me in a couple of ways. First, the
function it inlines is able to eat a lot more CPU time than I would
have expected. Second, the inlining does not seem to bloat the
kernel, at least in the configs folks have tested.
--
The following changes since commit 9ace4753a5202b02191d54e9fdf7f9e3d02b85eb:
Linux 6.19-rc4 (2026-01-04 14:41:55 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_misc_for_7.0-rc1
for you to fetch changes up to 6b32c93560cb194e10279bd3be3c1d0fa30df3e7:
x86/traps: Print unhashed pointers on stack overflow (2026-01-14 16:31:53 +0100)
----------------------------------------------------------------
* Inline x86-specific IPv6 checksum helper
* Update IOMMU docs to use stable identifiers
* Print unhashed pointers on fatal stack overflows
----------------------------------------------------------------
Eric Dumazet (1):
x86/lib: Inline csum_ipv6_magic()
Richard Lyu (1):
Documentation/x86: Update IOMMU spec references to use stable identifiers
Ryosuke Yasuoka (1):
x86/traps: Print unhashed pointers on stack overflow
Documentation/arch/x86/iommu.rst | 7 +++---
arch/x86/include/asm/checksum_64.h | 45 ++++++++++++++++++++++++++++----------
arch/x86/kernel/traps.c | 2 +-
arch/x86/lib/csum-wrappers_64.c | 22 -------------------
4 files changed, 38 insertions(+), 38 deletions(-)
next reply other threads:[~2026-02-09 21:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 21:10 Dave Hansen [this message]
2026-02-11 3:57 ` [GIT PULL] x86/misc for 7.0-rc1 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=20260209211003.2330804-1-dave.hansen@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--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