FYI, we noticed a +1445 bytes kernel size regression due to commit: commit: d50ba5357cba1a4c27916f444f41a3c272644168 (perf/x86/intel/lbr: Support Architectural LBRs) Details as below (size data is obtained by `nm --size-sort vmlinux`): 1193a053: x86/cpufeatures: Add Architectural LBRs feature bit d50ba535: perf/x86/intel/lbr: Support Architectural LBRs +---------------------------------+----------+----------+-------+ | symbol | 1193a053 | d50ba535 | delta | +---------------------------------+----------+----------+-------+ | bzImage | 439968 | 440672 | 704 | | nm.T.intel_pmu_lbr_read | 851 | 1324 | 473 | | nm.T.intel_pmu_arch_lbr_init | 0 | 339 | 339 | | nm.T.intel_pmu_init | 4493 | 4620 | 127 | | nm.T.intel_pmu_setup_lbr_filter | 491 | 615 | 124 | | nm.T.intel_pmu_lbr_enable_all | 122 | 245 | 123 | | nm.T.intel_pmu_lbr_sched_task | 554 | 637 | 83 | | nm.d.arch_lbr_ctl_map | 0 | 68 | 68 | | nm.d.arch_lbr_br_type_map | 0 | 64 | 64 | | nm.T.intel_pmu_lbr_reset | 142 | 169 | 27 | | nm.t.intel_pmu_lbr_filter | 430 | 448 | 18 | | nm.D.x86_pmu | 340 | 356 | 16 | | nm.t.intel_pmu_cpu_starting | 256 | 269 | 13 | | nm.T.intel_cpuc_prepare | 227 | 236 | 9 | | nm.T.intel_pmu_lbr_disable_all | 39 | 33 | -6 | | nm.t.wrlbr_from | 33 | 0 | -33 | +---------------------------------+----------+----------+-------+ Thanks, Kbuild test robot