FYI, we noticed a +919 bytes kernel size regression due to commit: commit: bf730bec0c108978e0a53d1ba7fb55ebf43dea9f (perf: Sharing PMU counters across compatible events) Details as below (size data is obtained by `nm --size-sort vmlinux`): de620fb9: Merge branch 'for-5.4-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup bf730bec: perf: Sharing PMU counters across compatible events +----------------------------------+----------+----------+-------+ | symbol | de620fb9 | bf730bec | delta | +----------------------------------+----------+----------+-------+ | nm.t.__perf_event_disable | 81 | 406 | 325 | | bzImage | 438976 | 439296 | 320 | | nm.t.list_add_event | 126 | 408 | 282 | | nm.t.event_sync_dup_count | 0 | 178 | 178 | | nm.t.event_sched_in | 285 | 395 | 110 | | nm.t.event_sched_out | 181 | 261 | 80 | | nm.t.perf_event_count | 0 | 68 | 68 | | nm.t.__perf_remove_from_context | 95 | 141 | 46 | | nm.t.inherit_event | 364 | 391 | 27 | | nm.t.event_pmu_read | 0 | 21 | 21 | | nm.T.perf_event_read_local | 286 | 298 | 12 | | nm.t.__perf_event_read | 160 | 163 | 3 | | nm.t.perf_event_stop | 51 | 53 | 2 | | nm.t.__perf_event_stop | 61 | 63 | 2 | | nm.t.__perf_event_period | 184 | 186 | 2 | | nm.t.perf_event_update_time | 96 | 95 | -1 | | nm.t.calc_timer_values | 115 | 114 | -1 | | nm.D.linux_banner | 119 | 118 | -1 | | nm.T.__perf_event_task_sched_out | 750 | 749 | -1 | | nm.t.__perf_install_in_context | 177 | 173 | -4 | | nm.t.perf_swevent_hrtimer | 307 | 303 | -4 | | nm.T.perf_event_update_userpage | 214 | 193 | -21 | | nm.t.__perf_event_read_value | 289 | 261 | -28 | | nm.t.__perf_read_group_add | 331 | 281 | -50 | | nm.T.perf_event_exit_task | 583 | 529 | -54 | | nm.t.perf_output_read | 608 | 534 | -74 | +----------------------------------+----------+----------+-------+ Thanks, Kbuild test robot