FYI, we noticed a +880 bytes kernel size regression due to commit: commit: f04158a22dfa771649f3a89beb30f9028db28c17 (perf: Allocate space in task_struct for pmu specific data) Details as below (size data is obtained by `nm --size-sort vmlinux`): 8b2214ec: change Makefile f04158a2: perf: Allocate space in task_struct for pmu specific data +----------------------------+----------+----------+-------+ | symbol | 8b2214ec | f04158a2 | delta | +----------------------------+----------+----------+-------+ | bzImage | 438720 | 439104 | 384 | | nm.t.perf_event_alloc | 1595 | 1889 | 294 | | nm.t.get_task_ctx_data_rcu | 0 | 176 | 176 | | nm.t._free_event | 410 | 545 | 135 | | nm.t.put_task_ctx_data_rcu | 0 | 112 | 112 | | nm.T.perf_event_fork | 20 | 118 | 98 | | nm.t.free_ctx_data | 0 | 19 | 19 | | nm.T.perf_event_exit_task | 583 | 601 | 18 | | nm.T.perf_event_init_task | 438 | 448 | 10 | | nm.t.perf_read | 474 | 481 | 7 | | nm.t.inherit_event | 357 | 362 | 5 | | nm.t.find_get_context | 359 | 364 | 5 | | nm.b.nr_task_data_events | 0 | 4 | 4 | | nm.D.linux_banner | 119 | 118 | -1 | | nm.t.kzalloc | 10 | 8 | -2 | +----------------------------+----------+----------+-------+ Thanks, Kbuild test robot