Changes in Makefile.autofdo

b2128290c29902315e632ea59e0504d6bc9e9b42 - Merge remote-tracking branch 'drm/drm-next' into msm-next-backmerge

Sat, 18 Jul 2026 17:06:55 +0200

Merge remote-tracking branch 'drm/drm-next' into msm-next-backmergeBackmerge of drm-next, mainly to pick up dt bindings docs updates toavoid conflicts.Signed-off-by: Rob Clark List of files: /linux/scripts/Makefile.autofdo

637315cb400eed1dbe721954fea437a61a2d65b2 - Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEAD

Tue, 18 Aug 2026 13:07:31 +0200

Merge tag 'kvm-riscv-7.3-1' of https://github.com/kvm-riscv/linux into HEADKVM/riscv changes for 7.3- Svadu/Zicfiss/Zicfilp FWFT support for Guest- Use try_cmpxchg for IMSIC MRIF RMW- More arch-specific tracepoints in KVM RISC-V- Eager Page Splitting for KVM RISC-V- Optimize hfence request handling for SMP Guests- Improve dirty log clearing by skipping zero bits in mask- Guard HFENCE range loops against overflow- CPU PM notifiers in KVM RISC-V for non-retentive idle states- Fix kernel-mode vector context save/restore for Guest List of files: /linux/scripts/Makefile.autofdo

efe86f088f48f18c27b648e5724048947f3b7fb4 - Merge drm/drm-next into drm-xe-next

Tue, 14 Jul 2026 15:40:31 +0200

Merge drm/drm-next into drm-xe-nextSync some i915/display changesSigned-off-by: Rodrigo Vivi List of files: /linux/scripts/Makefile.autofdo

6d177908bad5992e17669030db41caab88041d5e - Merge drm/drm-next into drm-intel-next

Tue, 30 Jun 2026 14:55:43 +0200

Merge drm/drm-next into drm-intel-nextSync with v7.2-rc1.Signed-off-by: Jani Nikula List of files: /linux/scripts/Makefile.autofdo

827b9aabd3ea3e96d5e48abed9f44dbd1e550d4e - Merge drm/drm-next into drm-misc-next

Tue, 30 Jun 2026 10:16:00 +0200

Merge drm/drm-next into drm-misc-nextBackmerging to get drm-misc-next to v7.2-rc1.Signed-off-by: Thomas Zimmermann List of files: /linux/scripts/Makefile.autofdo

7dd19adaaac9a161723a24de7c270861063ec6ac - Merge tag 'v7.2-rc1' into drm-rust-next

Sun, 28 Jun 2026 22:39:43 +0200

Merge tag 'v7.2-rc1' into drm-rust-nextMerge v7.2-rc1 into drm-rust-next to start the next cycle.Devres now requires T: 'static, which conflicts with shmem::Object usingDevres> without that bound. Resolve by adding 'staticas a supertrait to DriverObject and DeviceContext, which does notrestrict any current use cases since DriverObject is always implementedon owned, refcounted types and DeviceContext is a sealed marker traitwith only unit-type implementors.If DriverObject (or DeviceContext) ever becomes lifetime-parameterized(e.g. via a GAT for TTM backed objects), the 'static supertrait can berelaxed at that point.Signed-off-by: Danilo Krummrich List of files: /linux/scripts/Makefile.autofdo

0eaed89c18aeedf0898baf2dbf5ff027c6795152 - Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource

Mon, 17 Aug 2026 10:29:52 +0200

Merge tag 'timers-v7.3-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/daniel.lezcano/linux into timers/clocksource - Use designated initializers for sh_mtu2, sh_cmt, and sh_tmu, and drop the unused initializer in the platform_device_id table for sh_mtu2 (Uwe Kleine-König) - Remove redundant dev_err()/dev_err_probe() messages when devm_request_*_irq() fails, as the helper already logs an error message (Pan Chuang) - Fix a boot hang on Allwinner D1 when a forced minimum delta is used with the sun4i timer (Felix Yan) - Fix an IRQ leak in the cpuhp_setup_state() error path by freeing the IRQ on failure in the NXP PIT driver (WenTao Liang) - Fix incorrect unmapping of shared MMIO between the clocksource and clockevent drivers. If one of them fails to initialize, the error path unmaps the shared MMIO region, leaving the other driver with an invalid mapping on clps711x (Guangshuo Li) - Make the samsung_pwm driver compatible with PREEMPT_RT by replacing regular spinlocks with raw_spinlock_t in atomic contexts (Marek Szyprowski) - Use __raw_readl() and __raw_writel() instead of ioread32() and iowrite32() to support SWAP_IO_SPACE in the rtl-otto driver (Rustam Adilov) - Fix a missing clk_disable_unprepare() call in the timer initialization error path of the Armada driver (Yuho Choi)Link: https://lore.kernel.org/lkml/75feea31-683d-45a1-87f4-ab045e0152ae@oss.qualcomm.com List of files: /linux/scripts/Makefile.autofdo

b4d85f863e5a6f1fa01b186001af0f68f4f5239e - Merge branch 'next' into for-linus

Sat, 15 Aug 2026 06:26:07 +0200

Merge branch 'next' into for-linusPrepare input updates for 7.3 merge window. List of files: /linux/scripts/Makefile.autofdo

76904fccf81936c084faebc73ac72c0919a42941 - Merge tag 'v7.2-rc3' into next

Tue, 14 Jul 2026 04:06:00 +0200

Merge tag 'v7.2-rc3' into nextSync up with mainline to pull in stable fixes to avoid merge conflicts. List of files: /linux/scripts/Makefile.autofdo

00599d4841790d05401820a96cf7edb193888b00 - Merge drm/drm-fixes into drm-misc-fixes

Mon, 29 Jun 2026 17:58:00 +0200

Merge drm/drm-fixes into drm-misc-fixesPull in tag v7.2-rc1 so that drm-misc-fixes becomes useful again,and drm-misc-next-fixes can be closed.Signed-off-by: Maarten Lankhorst List of files: /linux/scripts/Makefile.autofdo

b079329b8691768962aa514b8f8c9077ca352459 - Merge tag 'rust-7.2' of gitolite.kernel.org:pub/scm/linux/kernel/git/ojeda/linux

Mon, 15 Jun 2026 05:55:48 +0200

Merge tag 'rust-7.2' of gitolite.kernel.org:pub/scm/linux/kernel/git/ojeda/linuxPull Rust updates from Miguel Ojeda: "This one is big due to the vendoring of the `zerocopy` library, which allows us to replace a bunch of `unsafe` code dealing with conversions between byte sequences and other types with safe alternatives. More details on that below (and in its merge commit). Toolchain and infrastructure: - Introduce support for the 'zerocopy' library [1][2]: Fast, safe, compile error. Pick two. Zerocopy makes zero-cost memory manipulation effortless. We write `unsafe` so you don't have to. It essentially provides derivable traits (e.g. 'FromBytes') and macros (e.g. 'transmute!') for safely converting between byte sequences and other types. Having such support allows us to remove some 'unsafe' code. It is among the most downloaded Rust crates and it is also used by the Rust compiler itself. It is licensed under "BSD-2-Clause OR Apache-2.0 OR MIT". The crates are imported essentially as-is (only +2/-3 lines needed to be adapted), plus SPDX identifiers. Upstream has since added the SPDX identifiers as well as one of the tweaks at my request, thus reducing our future diffs on updates -- I keep the details in one of our usual live lists [3]. In total, it is about ~39k lines added, ~32k without counting 'benches/' which are just for documentation purposes. The series includes a few Kbuild and rust-analyzer improvements and an example patch using it in Nova, removing one 'unsafe impl'. I checked that the codegen of an isolated example function (similar to the Nova patch on top) is essentially identical. It also turns out that (for that particular case) the 'zerocopy' version, even with 'debug-assertions' enabled, has no remaining panics, unlike a few in the current code (since the compiler can prove the remaining 'ub_checks' statically). So their "fast, safe" does indeed check out -- at least in that case. - Support AutoFDO. This allows Rust code to be profiled and optimized based on the profile. Tested with Rust Binder: ~13% slower without AutoFDO in the binderAddInts benchmark (using an app-launch benchmark for the profile). - Support Software Tag-Based KASAN. In addition, fix KASAN Kconfig by requiring Clang. - Add Kconfig options for each existing Rust KUnit test suite, such as 'CONFIG_RUST_BITMAP_KUNIT_TEST'. They are placed within a new menu, 'CONFIG_RUST_KUNIT_TESTS', in the new 'rust/kernel/Kconfig.test' file. - Support the upcoming Rust 1.98.0 release (expected 2026-08-20): lint cleanups and an unstable flag rename. - Disable 'rustdoc' documentation inlining for all prelude items, which bloats the generated documentation. - Ignore (in Git) and clean (in Kbuild) the (rarely) 'rustc'-generated '*.long-type-*.txt' files. 'kernel' crate: - Add new 'bitfield' module with the 'bitfield!' macro (extracted from the existing 'register!' one), which declares integer types that are split into distinct bit fields of arbitrary length. Each field is a 'Bounded' of the appropriate bit width (ensuring values are properly validated and avoiding implicit data loss) and gets several generated getters and setters (infallible, 'const' and fallible) as well as associated constants ('_MASK', '_SHIFT' and '_RANGE'). It also supports fields that can be converted from/to custom types, either fallibly ('?=>') or infallibly ('=>'). For instance: bitfield! { struct Rgb(u16) { 15:11 blue; 10:5 green; 4:0 red; } } // Compile-time checks. let color = Rgb::zeroed().with_const_green::<0x1f>(); assert_eq!(color.green(), 0x1f); assert_eq!(color.into_raw(), 0x1f << Rgb::GREEN_SHIFT); Add as well documentation and a test suite for it, as usual; and update the 'register!' macro to use it. It will be maintained by Alexandre Courbot (with Yury Norov as reviewer) under a new 'MAINTAINERS' entry: 'RUST [BITFIELD]'. - 'ptr' module: rework index projection syntax into keyworded syntax and introduce panicking variant. The keyword syntax ('build:', 'try:', 'panic:') is more explicit and paves the way of perhaps adding more flavors in the future, e.g. an 'unsafe' index projection. For instance, projections now look like this: fn f(p: *const [u8; 32]) -> Result { // Ok, within bounds, checked at build time. project!(p, [build: 1]); // Build error. project!(p, [build: 128]); // `OutOfBound` runtime error (convertible to `ERANGE`). project!(p, [try: 128]); // Runtime panic. project!(p, [panic: 128]); Ok(()) } Update as well the users, which now look like e.g. // Pointer to the first entry of the GSP message queue. let data = project!(self.0.as_ptr(), .gspq.msgq.data[build: 0]); - 'build_assert' module: make the module the home of its macros instead of rendering them twice. - 'sync' module: add 'UniqueArc::as_ptr()' associated function. - 'alloc' module: - Fix the 'Vec::reserve()' doctest to properly account for the existing vector length in the capacity assertion. - Fix an incorrect operator in the 'Vec::extend_with()' 'SAFETY' comment; add a doc test demonstrating basic usage and the zero-length case. - Clean imports across several modules to follow the "kernel vertical" import style in order to minimize conflicts. 'pin-init' crate: - User visible changes: - Do not generate 'non_snake_case' warnings for identifiers that are syntactically just users of a field name. This would allow all '#[allow(non_snake_case)]' in nova-core to be removed, which Gary will send to the nova tree next cycle. - Filter non-cfg attributes out properly in derived structs. This improves pin-init compatibility with other derive macros. - Insert projection types' where clause properly. - Other changes: - Bump MSRV to 1.82, plus associated cleanups. - Overhaul how init slots are projected. The new approach is easier to justify with safety comments. - Mark more functions as inline, which should help mitigate the super-long symbol name issue due to lack of inlining. rust-analyzer: - Support '--envs' for passing env vars for crates like 'zerocopy'. 'MAINTAINERS': - Add the following reviewers to the 'RUST' entry: - Daniel Almeida - Tamir Duberstein - Alexandre Courbot - Onur Özkan They have been involved in the Rust for Linux project for about 7 collective years and bring expertise across several domains, which will be very useful to have around in the future. Thanks everyone for stepping up! And some other fixes, cleanups and improvements"Link: https://github.com/google/zerocopy [1]Link: https://docs.rs/zerocopy [2]Link: https://github.com/Rust-for-Linux/linux/issues/1239 [3]* tag 'rust-7.2' of gitolite.kernel.org:pub/scm/linux/kernel/git/ojeda/linux: (86 commits) MAINTAINERS: add Onur Özkan as Rust reviewer MAINTAINERS: add Alexandre Courbot as Rust reviewer MAINTAINERS: add Tamir Duberstein as Rust reviewer MAINTAINERS: add Daniel Almeida as Rust reviewer kbuild: rust: clean `zerocopy-derive` in `mrproper` rust: make `build_assert` module the home of related macros rust: str: clean unused import for Rust >= 1.98 rust: str: use the "kernel vertical" imports style rust: aref: use the "kernel vertical" imports style rust: page: use the "kernel vertical" imports style gpu: nova-core: firmware: parse `FalconUCodeDescV2` via `zerocopy` rust: prelude: add `zerocopy{,_derive}::FromBytes` rust: zerocopy-derive: enable support in kbuild rust: zerocopy-derive: add `README.md` rust: zerocopy-derive: avoid generating non-ASCII identifiers rust: zerocopy-derive: add SPDX License Identifiers rust: zerocopy-derive: import crate rust: zerocopy: enable support in kbuild rust: zerocopy: add `README.md` rust: zerocopy: remove float `Display` support ... List of files: /linux/scripts/Makefile.autofdo

7594302d9ddd9f198173a658250e7b7debc6ed76 - kbuild: rust: rename flag to `-Zdebuginfo-for-profiling` for Rust >= 1.98

Tue, 02 Jun 2026 17:16:38 +0200

kbuild: rust: rename flag to `-Zdebuginfo-for-profiling` for Rust >= 1.98Starting with Rust 1.98.0 (expected 2026-08-20), the`-Zdebug-info-for-profiling` flag has been renamed to`-Zdebuginfo-for-profiling` (i.e. one less dash, to match `debuginfo`sin other flags) [1].Without this change, one gets in the latest nightlies: error: unknown unstable option: `debug-info-for-profiling`Thus pass the right name.Link: https://github.com/rust-lang/rust/pull/156887 [1]Reviewed-by: Alice Ryhl Acked-by: Nathan Chancellor Link: https://patch.msgid.link/20260602151638.14358-1-ojeda@kernel.orgSigned-off-by: Miguel Ojeda List of files: /linux/scripts/Makefile.autofdo

a960c2cdb19e237f284a3b96eb8a0359abcf0e63 - kbuild: rust: add AutoFDO support

Tue, 31 Mar 2026 12:57:49 +0200

kbuild: rust: add AutoFDO supportThis patch enables AutoFDO build support for Rust code within the Linuxkernel. This allows Rust code to be profiled and optimized based on theprofile.The RUSTFLAGS variable was suffixed with *_AUTOFDO_CLANG to match thenaming of the config option, which is called CONFIG_AUTOFDO_CLANG.This implementation has been verified in Android, first by inspectingthe object files and confirming that they look correct. After that,it was verified as below:1. Running the binderAddInts benchmark [1] with Rust Binder built as rust_binder.ko module, using a Pixel 9 Pro.2. Collecting a profile on a Pixel 10 Pro XL using the app-launch benchmark, which starts different apps many times, on a device with Rust Binder as a built-in kernel module. (C Binder was not present on the device.)3. Using the collected profile, run the binderAddInts benchmark again with Rust Binder built both as a rust_binder.ko module, and as a built-in kernel module.4. In both cases, Rust Binder without AutoFDO was approximately 13% slower than the AutoFDO optimized version. Built-in vs .ko did not make a measurable performance difference.All of the above was verified in conjunction with my helpers inliningseries [2], which confirmed that this worked correctly for helpers tooonce [3] was fixed in the helpers inlining series.Link: https://android.googlesource.com/platform/system/extras/+/920f089/tests/binder/benchmarks/binderAddInts.cpp [1]Link: https://lore.kernel.org/r/20260203-inline-helpers-v2-0-beb8547a03c9@google.com [2]Link: https://lore.kernel.org/r/aasPsbMEsX6iGUl8@google.com [3]Reviewed-by: Rong Xu Reviewed-by: Gary Guo Tested-by: Alice Ryhl Signed-off-by: Alice Ryhl Acked-by: Nicolas Schier Acked-by: Nathan Chancellor Link: https://patch.msgid.link/20260331-autofdo-v2-1-eb5c5964820d@google.com[ Reworded for typos. - Miguel ]Signed-off-by: Miguel Ojeda List of files: /linux/scripts/Makefile.autofdo

c771600c6af14749609b49565ffb4cac2959710d - Merge drm/drm-next into drm-intel-gt-next

Wed, 05 Feb 2025 10:29:14 +0100

Merge drm/drm-next into drm-intel-gt-nextWe need4ba4f1afb6a9 ("perf: Generic hotplug support for a PMU with a scope")in order to land a i915 PMU simplification and a fix. That landed in 6.12and we are stuck at 6.9 so lets bump things forward.Signed-off-by: Tvrtko Ursulin List of files: /linux/scripts/Makefile.autofdo

60675d4ca1ef0857e44eba5849b74a3a998d0c0f - Merge branch 'linus' into x86/mm, to pick up fixes

Fri, 20 Dec 2024 10:25:44 +0100

Merge branch 'linus' into x86/mm, to pick up fixesSigned-off-by: Ingo Molnar List of files: /linux/scripts/Makefile.autofdo

25768de50b1f2dbb6ea44bd5148a87fe2c9c3688 - Merge branch 'next' into for-linus

Tue, 21 Jan 2025 06:37:39 +0100

Merge branch 'next' into for-linusPrepare input updates for 6.14 merge window. List of files: /linux/scripts/Makefile.autofdo

670af65d2ab4a6a9bb72f014b080757e291ad3fe - Merge branch 'for-6.14/constify-bin-attribute' into for-linus

Mon, 20 Jan 2025 09:58:12 +0100

Merge branch 'for-6.14/constify-bin-attribute' into for-linus- constification of 'struct bin_attribute' in various HID driver (Thomas Weißschuh) List of files: /linux/scripts/Makefile.autofdo

6d4a0f4ea72319c9a37c1a7191695467006dd272 - Merge tag 'v6.13-rc3' into next

Tue, 17 Dec 2024 18:40:45 +0100

Merge tag 'v6.13-rc3' into nextSync up with the mainline. List of files: /linux/scripts/Makefile.autofdo

302cc446cbd92aadff72a647cebc13d5634f8342 - Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net

Thu, 05 Dec 2024 20:48:58 +0100

Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/netCross-merge networking fixes after downstream PR (net-6.13-rc2).No conflicts or adjacent changes.Signed-off-by: Jakub Kicinski List of files: /linux/scripts/Makefile.autofdo

c5fb51b71788926feef0d07f30c8af1d5e4af1a6 - Merge remote-tracking branch 'pm/opp/linux-next' into HEAD

Fri, 03 Jan 2025 16:13:45 +0100

Merge remote-tracking branch 'pm/opp/linux-next' into HEADMerge pm/opp tree to get dev_pm_opp_get_bw()Signed-off-by: Rob Clark List of files: /linux/scripts/Makefile.autofdo