Changes in Kconfig

eb5249b12507246dc959945454cd1be8d7dc3795 - Merge tag 'parisc-for-7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux

Sat, 18 Apr 2026 20:37:36 +0200

Merge tag 'parisc-for-7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linuxPull parisc architecture updates from Helge Deller: - A fix to make modules on 32-bit parisc architecture work again - Drop ip_fast_csum() inline assembly to avoid unaligned memory accesses - Allow to build kernel without 32-bit VDSO - Reference leak fix in error path in LED driver* tag 'parisc-for-7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux: parisc: led: fix reference leak on failed device registration module.lds.S: Fix modules on 32-bit parisc architecture parisc: Allow to build without VDSO32 parisc: Include 32-bit VDSO only when building for 32-bit or compat mode parisc: Allow to disable COMPAT mode on 64-bit kernel parisc: Fix default stack size when COMPAT=n parisc: Fix signal code to depend on CONFIG_COMPAT instead of CONFIG_64BIT parisc: is_compat_task() shall return false for COMPAT=n parisc: Avoid compat syscalls when COMPAT=n parisc: _llseek syscall is only available for 32-bit userspace parisc: Drop ip_fast_csum() inline assembly implementation parisc: update outdated comments for renamed ccio_alloc_consistent() List of files: /linux/arch/Kconfig

9cdca336677b4d15579ec462e33c8a330ab3a9de - Merge tag 'integrity-v7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity

Sat, 18 Apr 2026 00:42:01 +0200

Merge tag 'integrity-v7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrityPull integrity updates from Mimi Zohar: "There are two main changes, one feature removal, some code cleanup, and a number of bug fixes. Main changes: - Detecting secure boot mode was limited to IMA. Make detecting secure boot mode accessible to EVM and other LSMs - IMA sigv3 support was limited to fsverity. Add IMA sigv3 support for IMA regular file hashes and EVM portable signatures Remove: - Remove IMA support for asychronous hash calculation originally added for hardware acceleration Cleanup: - Remove unnecessary Kconfig CONFIG_MODULE_SIG and CONFIG_KEXEC_SIG tests - Add descriptions of the IMA atomic flags Bug fixes: - Like IMA, properly limit EVM "fix" mode - Define and call evm_fix_hmac() to update security.evm - Fallback to using i_version to detect file change for filesystems that do not support STATX_CHANGE_COOKIE - Address missing kernel support for configured (new) TPM hash algorithms - Add missing crypto_shash_final() return value"* tag 'integrity-v7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity: evm: Enforce signatures version 3 with new EVM policy 'bit 3' integrity: Allow sigv3 verification on EVM_XATTR_PORTABLE_DIGSIG ima: add support to require IMA sigv3 signatures ima: add regular file data hash signature version 3 support ima: Define asymmetric_verify_v3() to verify IMA sigv3 signatures ima: remove buggy support for asynchronous hashes integrity: Eliminate weak definition of arch_get_secureboot() ima: Add code comments to explain IMA iint cache atomic_flags ima_fs: Correctly create securityfs files for unsupported hash algos ima: check return value of crypto_shash_final() in boot aggregate ima: Define and use a digest_size field in the ima_algo_desc structure powerpc/ima: Drop unnecessary check for CONFIG_MODULE_SIG ima: efi: Drop unnecessary check for CONFIG_MODULE_SIG/CONFIG_KEXEC_SIG ima: fallback to using i_version to detect file change evm: fix security.evm for a file with IMA signature s390: Drop unnecessary CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT evm: Don't enable fix mode when secure boot is enabled integrity: Make arch_ima_get_secureboot integrity-wide List of files: /linux/arch/Kconfig

1221365f55281349da4f4ba41c05b57cd15f5c28 - module.lds.S: Fix modules on 32-bit parisc architecture

Tue, 07 Apr 2026 22:07:22 +0200

module.lds.S: Fix modules on 32-bit parisc architectureOn the 32-bit parisc architecture, we always used the-ffunction-sections compiler option to tell the compiler to put thefunctions into seperate text sections. This is necessary, otherwise"big" kernel modules like ext4 or ipv6 fail to load because somebranches won't be able to reach their stubs.Commit 1ba9f8979426 ("vmlinux.lds: Unify TEXT_MAIN, DATA_MAIN, and relatedmacros") broke this for parisc because all text sections will getunconditionally merged now.Introduce the ARCH_WANTS_MODULES_TEXT_SECTIONS config option whichavoids the text section merge for modules, and fix this issue byenabling this option by default for 32-bit parisc.Fixes: 1ba9f8979426 ("vmlinux.lds: Unify TEXT_MAIN, DATA_MAIN, and related macros")Cc: Josh Poimboeuf Cc: stable@vger.kernel.org # v6.19+Suggested-by: Sami Tolvanen Reviewed-by: Petr Pavlu Signed-off-by: Helge Deller List of files: /linux/arch/Kconfig

d568788baab24875604c231f723dbb72387fb081 - Merge tag 'hardening-v7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux

Tue, 14 Apr 2026 02:52:29 +0200

Merge tag 'hardening-v7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linuxPull hardening updates from Kees Cook: - randomize_kstack: Improve implementation across arches (Ryan Roberts) - lkdtm/fortify: Drop unneeded FORTIFY_STR_OBJECT test - refcount: Remove unused __signed_wrap function annotations* tag 'hardening-v7.1-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux: lkdtm/fortify: Drop unneeded FORTIFY_STR_OBJECT test refcount: Remove unused __signed_wrap function annotations randomize_kstack: Unify random source across arches randomize_kstack: Maintain kstack_offset per task List of files: /linux/arch/Kconfig

26ff969926a08eee069767ddbbbc301adbcd9676 - Merge tag 'rust-7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux

Mon, 13 Apr 2026 18:54:20 +0200

Merge tag 'rust-7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linuxPull Rust updates from Miguel Ojeda: "Toolchain and infrastructure: - Bump the minimum Rust version to 1.85.0 (and 'bindgen' to 0.71.1). As proposed in LPC 2025 and the Maintainers Summit [1], we are going to follow Debian Stable's Rust versions as our minimum versions. Debian Trixie was released on 2025-08-09 with a Rust 1.85.0 and 'bindgen' 0.71.1 toolchain, which is a fair amount of time for e.g. kernel developers to upgrade. Other major distributions support a Rust version that is high enough as well, including: + Arch Linux. + Fedora Linux. + Gentoo Linux. + Nix. + openSUSE Slowroll and openSUSE Tumbleweed. + Ubuntu 25.10 and 26.04 LTS. In addition, 24.04 LTS using their versioned packages. The merged patch series comes with the associated cleanups and simplifications treewide that can be performed thanks to both bumps, as well as documentation updates. In addition, start using 'bindgen''s '--with-attribute-custom-enum' feature to set the 'cfi_encoding' attribute for the 'lru_status' enum used in Binder. Link: https://lwn.net/Articles/1050174/ [1] - Add experimental Kconfig option ('CONFIG_RUST_INLINE_HELPERS') that inlines C helpers into Rust. Essentially, it performs a step similar to LTO, but just for the helpers, i.e. very local and fast. It relies on 'llvm-link' and its '--internalize' flag, and requires a compatible LLVM between Clang and 'rustc' (i.e. same major version, 'CONFIG_RUSTC_CLANG_LLVM_COMPATIBLE'). It is only enabled for two architectures for now. The result is a measurable speedup in different workloads that different users have tested. For instance, for the null block driver, it amounts to a 2%. - Support global per-version flags. While we already have per-version flags in many places, we didn't have a place to set global ones that depend on the compiler version, i.e. in 'rust_common_flags', which sometimes is needed to e.g. tweak the lints set per version. Use that to allow the 'clippy::precedence' lint for Rust < 1.86.0, since it had a change in behavior. - Support overriding the crate name and apply it to Rust Binder, which wanted the module to be called 'rust_binder'. - Add the remaining '__rust_helper' annotations (started in the previous cycle). 'kernel' crate: - Introduce the 'const_assert!' macro: a more powerful version of 'static_assert!' that can refer to generics inside functions or implementation bodies, e.g.: fn f() { const_assert!(N > 1); } fn g() { const_assert!(size_of::() > 0, "T cannot be ZST"); } In addition, reorganize our set of build-time assertion macros ('{build,const,static_assert}!') to live in the 'build_assert' module. Finally, improve the docs as well to clarify how these are different from one another and how to pick the right one to use, and their equivalence (if any) to the existing C ones for extra clarity. - 'sizes' module: add 'SizeConstants' trait. This gives us typed 'SZ_*' constants (avoiding casts) for use in device address spaces where the address width depends on the hardware (e.g. 32-bit MMIO windows, 64-bit GPU framebuffers, etc.), e.g.: let gpu_heap = 14 * u64::SZ_1M; let mmio_window = u32::SZ_16M; - 'clk' module: implement 'Send' and 'Sync' for 'Clk' and thus simplify the users in Tyr and PWM. - 'ptr' module: add 'const_align_up'. - 'str' module: improve the documentation of the 'c_str!' macro to explain that one should only use it for non-literal cases (for the other case we instead use C string literals, e.g. 'c"abc"'). - Disallow the use of 'CStr::{as_ptr,from_ptr}' and clean one such use in the 'task' module. - 'sync' module: finish the move of 'ARef' and 'AlwaysRefCounted' outside of the 'types' module, i.e. update the last remaining instances and finally remove the re-exports. - 'error' module: clarify that 'from_err_ptr' can return 'Ok(NULL)', including runtime-tested examples. The intention is to hopefully prevent UB that assumes the result of the function is not 'NULL' if successful. This originated from a case of UB I noticed in 'regulator' that created a 'NonNull' on it. Timekeeping: - Expand the example section in the 'HrTimer' documentation. - Mark the 'ClockSource' trait as unsafe to ensure valid values for 'ktime_get()'. - Add 'Delta::from_nanos()'. 'pin-init' crate: - Replace the 'Zeroable' impls for 'Option' with impls of 'ZeroableOption' for 'NonZero*'. - Improve feature gate handling for unstable features. - Declutter the documentation of implementations of 'Zeroable' for tuples. - Replace uses of 'addr_of[_mut]!' with '&raw [mut]'. rust-analyzer: - Add type annotations to 'generate_rust_analyzer.py'. - Add support for scripts written in Rust ('generate_rust_target.rs', 'rustdoc_test_builder.rs', 'rustdoc_test_gen.rs'). - Refactor 'generate_rust_analyzer.py' to explicitly identify host and target crates, improve readability, and reduce duplication. And some other fixes, cleanups and improvements"* tag 'rust-7.1' of git://git.kernel.org/pub/scm/linux/kernel/git/ojeda/linux: (79 commits) rust: sizes: add SizeConstants trait for device address space constants rust: kernel: update `file_with_nul` comment rust: kbuild: allow `clippy::precedence` for Rust < 1.86.0 rust: kbuild: support global per-version flags rust: declare cfi_encoding for lru_status docs: rust: general-information: use real example docs: rust: general-information: simplify Kconfig example docs: rust: quick-start: remove GDB/Binutils mention docs: rust: quick-start: remove Nix "unstable channel" note docs: rust: quick-start: remove Gentoo "testing" note docs: rust: quick-start: add Ubuntu 26.04 LTS and remove subsection title docs: rust: quick-start: update minimum Ubuntu version docs: rust: quick-start: update Ubuntu versioned packages docs: rust: quick-start: openSUSE provides `rust-src` package nowadays rust: kbuild: remove "dummy parameter" workaround for `bindgen` < 0.71.1 rust: kbuild: update `bindgen --rust-target` version and replace comment rust: rust_is_available: remove warning for `bindgen` < 0.69.5 && libclang >= 19.1 rust: rust_is_available: remove warning for `bindgen` 0.66.[01] rust: bump `bindgen` minimum supported version to 0.71.1 (Debian Trixie) rust: block: update `const_refs_to_static` MSRV TODO comment ... List of files: /linux/arch/Kconfig

7ab26eb5a2b4009344580117ef05981867e0c7d7 - Merge patch series "rust: bump minimum Rust and `bindgen` versions"

Tue, 07 Apr 2026 10:40:11 +0200

Merge patch series "rust: bump minimum Rust and `bindgen` versions"As proposed in the past in e.g. LPC 2025 and the Maintainers Summit [1],we are going to follow Debian Stable's Rust versions as our minimumsupported version.Debian Trixie was released with a Rust 1.85.0 toolchain [2], which itstill uses to this day [3] (i.e. no update to Rust 1.85.1).Debian Trixie was released with `bindgen` 0.71.1, which it also stilluses to this day [4].Debian Trixie's release happened on 2025-08-09 [5], which means that afair amount of time has passed since its release for kernel developersto upgrade.Thus bump the minimum to the new versions, i.e. - Rust: 1.78.0 -> 1.85.0 - bindgen: 0.65.1 -> 0.71.1There are a few main parts to the series, in this order: - A few cleanups that can be performed before the bumps. - The Rust bump (and its cleanups). - The `bindgen` bump (and its cleanups). - Documentation updates. - The `cfi_encoding` patch, added here, which needs the bump. - The per-version flags support and a Clippy cleanup on top.Link: https://lwn.net/Articles/1050174/ [1]Link: https://www.debian.org/releases/trixie/release-notes/whats-new.en.html#desktops-and-well-known-packages [2]Link: https://packages.debian.org/trixie/rustc [3]Link: https://packages.debian.org/trixie/bindgen [4]Link: https://www.debian.org/releases/trixie/ [5]Link: https://patch.msgid.link/20260405235309.418950-1-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux/arch/Kconfig

b28711ac98e8b43bfbf5c918022018a54dcedd45 - rust: simplify `RUSTC_VERSION` Kconfig conditions

Mon, 06 Apr 2026 01:52:44 +0200

rust: simplify `RUSTC_VERSION` Kconfig conditionsWith the Rust version bump in place, several Kconfig conditions based on`RUSTC_VERSION` are always true.Thus simplify them.The minimum supported major LLVM version by our new Rust minimum versionis now LLVM 18, instead of LLVM 16. However, there are no possiblecleanups for `RUSTC_LLVM_VERSION`.Reviewed-by: Tamir Duberstein Reviewed-by: Gary Guo Link: https://patch.msgid.link/20260405235309.418950-9-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux/arch/Kconfig

a96ef5848cb096226bf6aff31a90d8b136d99b71 - randomize_kstack: Unify random source across arches

Tue, 03 Mar 2026 16:08:39 +0100

randomize_kstack: Unify random source across archesPreviously different architectures were using random sources ofdiffering strength and cost to decide the random kstack offset. A numberof architectures (loongarch, powerpc, s390, x86) were using theirtimestamp counter, at whatever the frequency happened to be. Otherarches (arm64, riscv) were using entropy from the crng viaget_random_u16().There have been concerns that in some cases the timestamp counters maybe too weak, because they can be easily guessed or influenced by userspace. And get_random_u16() has been shown to be too costly for thelevel of protection kstack offset randomization provides.So let's use a common, architecture-agnostic source of entropy; aper-cpu prng, seeded at boot-time from the crng. This has a fewbenefits: - We can remove choose_random_kstack_offset(); That was only there to try to make the timestamp counter value a bit harder to influence from user space [*]. - The architecture code is simplified. All it has to do now is call add_random_kstack_offset() in the syscall path. - The strength of the randomness can be reasoned about independently of the architecture. - Arches previously using get_random_u16() now have much faster syscall paths, see below results.[*] Additionally, this gets rid of some redundant work on s390 and x86.Before this patch, those architectures calledchoose_random_kstack_offset() under arch_exit_to_user_mode_prepare(),which is also called for exception returns to userspace which were *not*syscalls (e.g. regular interrupts). Getting rid ofchoose_random_kstack_offset() avoids a small amount of redundant workfor the non-syscall cases.In some configurations, add_random_kstack_offset() will now callinstrumentable code, so for a couple of arches, I have moved the call abit later to the first point where instrumentation is allowed. Thisdoesn't impact the efficacy of the mechanism.There have been some claims that a prng may be less strong than thetimestamp counter if not regularly reseeded. But the prng has a periodof about 2^113. So as long as the prng state remains secret, it shouldnot be possible to guess. If the prng state can be accessed, we havebigger problems.Additionally, we are only consuming 6 bits to randomize the stack, sothere are only 64 possible random offsets. I assert that it would betrivial for an attacker to brute force by repeating their attack andwaiting for the random stack offset to be the desired one. The prngapproach seems entirely proportional to this level of protection.Performance data are provided below. The baseline is v6.18 with rndstackon for each respective arch. (I)/(R) indicate statistically significantimprovement/regression. arm64 platform is AWS Graviton3 (m7g.metal).x86_64 platform is AWS Sapphire Rapids (m7i.24xlarge):+-----------------+--------------+---------------+---------------+| Benchmark | Result Class | per-cpu-prng | per-cpu-prng || | | arm64 (metal) | x86_64 (VM) |+=================+==============+===============+===============+| syscall/getpid | mean (ns) | (I) -9.50% | (I) -17.65% || | p99 (ns) | (I) -59.24% | (I) -24.41% || | p99.9 (ns) | (I) -59.52% | (I) -28.52% |+-----------------+--------------+---------------+---------------+| syscall/getppid | mean (ns) | (I) -9.52% | (I) -19.24% || | p99 (ns) | (I) -59.25% | (I) -25.03% || | p99.9 (ns) | (I) -59.50% | (I) -28.17% |+-----------------+--------------+---------------+---------------+| syscall/invalid | mean (ns) | (I) -10.31% | (I) -18.56% || | p99 (ns) | (I) -60.79% | (I) -20.06% || | p99.9 (ns) | (I) -61.04% | (I) -25.04% |+-----------------+--------------+---------------+---------------+I tested an earlier version of this change on x86 bare metal and itshowed a smaller but still significant improvement. The bare metalsystem wasn't available this time around so testing was done in a VMinstance. I'm guessing the cost of rdtsc is higher for VMs.Acked-by: Mark Rutland Signed-off-by: Ryan Roberts Link: https://patch.msgid.link/20260303150840.3789438-3-ryan.roberts@arm.comSigned-off-by: Kees Cook List of files: /linux/arch/Kconfig

7caedbb5ade345df0eec0bf01035c780919a9f56 - integrity: Eliminate weak definition of arch_get_secureboot()

Mon, 09 Mar 2026 21:37:02 +0100

integrity: Eliminate weak definition of arch_get_secureboot()security/integrity/secure_boot.c contains a single __weak function,which breaks recordmcount when building with clang: $ make -skj"$(nproc)" ARCH=powerpc LLVM=1 ppc64_defconfig security/integrity/secure_boot.o Cannot find symbol for section 2: .text. security/integrity/secure_boot.o: failedIntroduce a Kconfig symbol, CONFIG_HAVE_ARCH_GET_SECUREBOOT, to indicatethat an architecture provides a definition of arch_get_secureboot().Provide a static inline stub when this symbol is not defined to achievethe same effect as the __weak function, allowing secure_boot.c to beremoved altogether. Move the s390 definition of arch_get_secureboot()out of the CONFIG_KEXEC_FILE block to ensure it is always available, asit does not actually depend on KEXEC_FILE.Reported-by: Arnd Bergmann Fixes: 31a6a07eefeb ("integrity: Make arch_ima_get_secureboot integrity-wide")Signed-off-by: Nathan Chancellor Acked-by: Arnd Bergmann Signed-off-by: Mimi Zohar List of files: /linux/arch/Kconfig

42d3b66d4cdbacfc9d120d2301b8de89cc29a914 - Merge drm/drm-next into drm-xe-next

Thu, 12 Mar 2026 15:17:56 +0100

Merge drm/drm-next into drm-xe-nextBackmerging to bring in 7.00-rc3. Important ahead GPU SVM merging THPsupport.Signed-off-by: Matthew Brost List of files: /linux/arch/Kconfig

f09812b85fa6f41058bcc46e70ac406bf9b0493a - Merge drm/drm-next into drm-intel-next

Wed, 25 Feb 2026 12:23:04 +0100

Merge drm/drm-next into drm-intel-nextSync with v7.0-rc1 which contains a few treewide changes affecting i915.Signed-off-by: Jani Nikula List of files: /linux/arch/Kconfig

8b85987d3cf50178f67618122d9f3bb202f62f42 - Merge drm/drm-next into drm-misc-next

Mon, 23 Feb 2026 11:48:20 +0100

Merge drm/drm-next into drm-misc-nextLet's merge 7.0-rc1 to start the new drm-misc-next windowSigned-off-by: Maxime Ripard List of files: /linux/arch/Kconfig

c17ee635fd3a482b2ad2bf5e269755c2eae5f25e - Merge drm/drm-fixes into drm-misc-fixes

Mon, 23 Feb 2026 10:09:45 +0100

Merge drm/drm-fixes into drm-misc-fixes7.0-rc1 was just released, let's merge it to kick the new release cycle.Signed-off-by: Maxime Ripard List of files: /linux/arch/Kconfig

57cb845067e0bf5d42af6bc570190bba3238660e - Merge tag 'x86_paravirt_for_v7.0_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip

Wed, 11 Feb 2026 04:01:45 +0100

Merge tag 'x86_paravirt_for_v7.0_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tipPull x86 paravirt updates from Borislav Petkov: - A nice cleanup to the paravirt code containing a unification of the paravirt clock interface, taming the include hell by splitting the pv_ops structure and removing of a bunch of obsolete code (Juergen Gross)* tag 'x86_paravirt_for_v7.0_rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (23 commits) x86/paravirt: Use XOR r32,r32 to clear register in pv_vcpu_is_preempted() x86/paravirt: Remove trailing semicolons from alternative asm templates x86/pvlocks: Move paravirt spinlock functions into own header x86/paravirt: Specify pv_ops array in paravirt macros x86/paravirt: Allow pv-calls outside paravirt.h objtool: Allow multiple pv_ops arrays x86/xen: Drop xen_mmu_ops x86/xen: Drop xen_cpu_ops x86/xen: Drop xen_irq_ops x86/paravirt: Move pv_native_*() prototypes to paravirt.c x86/paravirt: Introduce new paravirt-base.h header x86/paravirt: Move paravirt_sched_clock() related code into tsc.c x86/paravirt: Use common code for paravirt_steal_clock() riscv/paravirt: Use common code for paravirt_steal_clock() loongarch/paravirt: Use common code for paravirt_steal_clock() arm64/paravirt: Use common code for paravirt_steal_clock() arm/paravirt: Use common code for paravirt_steal_clock() sched: Move clock related paravirt code to kernel/sched paravirt: Remove asm/paravirt_api_clock.h x86/paravirt: Move thunk macros to paravirt_types.h ... List of files: /linux/arch/Kconfig

ec496f77b4c11036cc835d6f045fb5e5ef1e6530 - Merge branch 'for-6.20/sony' into for-linus

Mon, 09 Feb 2026 17:33:26 +0100

Merge branch 'for-6.20/sony' into for-linus- Support for Rock band 4 PS4 and PS5 guitars (Rosalie Wanders) List of files: /linux/arch/Kconfig

cc4adab164b772a34b3340d644b7c4728498581e - Merge tag 'v6.19-rc1' into msm-next

Tue, 20 Jan 2026 23:06:55 +0100

Merge tag 'v6.19-rc1' into msm-nextMerge Linux 6.19-rc1 in order to catch up with other changes (e.g. UBWCconfig database defining UBWC_6).Signed-off-by: Dmitry Baryshkov List of files: /linux/arch/Kconfig

e6b2aa6d40045a3149071ca3af950ea8e6ff79c4 - sched: Move clock related paravirt code to kernel/sched

Mon, 05 Jan 2026 12:05:05 +0100

sched: Move clock related paravirt code to kernel/schedParavirt clock related functions are available in multiple archs.In order to share the common parts, move the common static keysto kernel/sched/ and remove them from the arch specific files.Make a common paravirt_steal_clock() implementation available inkernel/sched/cputime.c, guarding it with a new config optionCONFIG_HAVE_PV_STEAL_CLOCK_GEN, which can be selected by an archin case it wants to use that common variant.Signed-off-by: Juergen Gross Signed-off-by: Borislav Petkov (AMD) Acked-by: Peter Zijlstra (Intel) Link: https://patch.msgid.link/20260105110520.21356-7-jgross@suse.com List of files: /linux/arch/Kconfig

5add3c3c280a35f7e258e9cef7607db5a2e56fdc - Merge drm/drm-next into drm-xe-next

Fri, 19 Dec 2025 11:51:22 +0100

Merge drm/drm-next into drm-xe-nextBackmerging to bring in 6.19-rc1. An important upstream bugfix andto help unblock PTL CI.Signed-off-by: Thomas Hellström List of files: /linux/arch/Kconfig

ec439c38013550420aecc15988ae6acb670838c1 - Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf after 6.19-rc1

Wed, 17 Dec 2025 06:29:38 +0100

Merge git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf after 6.19-rc1Cross-merge BPF and other fixes after downstream PR.Signed-off-by: Alexei Starovoitov List of files: /linux/arch/Kconfig

b8304863a3990d0f18c38e5b94191830a63ee1af - Merge drm/drm-next into drm-intel-next

Mon, 15 Dec 2025 14:24:02 +0100

Merge drm/drm-next into drm-intel-nextSync-up some display code needed for Async flips refactor.Signed-off-by: Rodrigo Vivi List of files: /linux/arch/Kconfig