FYI, we noticed a +794 bytes kernel size regression due to commit:

commit: b473cfff35cb5ee0b14df47f88eca042489288ba (perf: Allocate space in task_struct for pmu specific data)
 

Details as below (size data is obtained by `nm --size-sort vmlinux`):

452c5636: change Makefile
b473cfff: perf: Allocate space in task_struct for pmu specific data

+---------------------------+----------+----------+-------+
|          symbol           | 452c5636 | b473cfff | delta |
+---------------------------+----------+----------+-------+
| bzImage                   | 438240   | 438656   | 416   |
| nm.t.perf_event_alloc     | 1559     | 1894     | 335   |
| nm.t._free_event          | 410      | 579      | 169   |
| nm.T.perf_event_fork      | 20       | 111      | 91    |
| nm.t.alloc_task_ctx_data  | 0        | 73       | 73    |
| nm.t.free_task_ctx_data   | 0        | 33       | 33    |
| nm.T.perf_event_exit_task | 583      | 614      | 31    |
| nm.T.perf_event_init_task | 438      | 458      | 20    |
| nm.t.free_ctx_data        | 0        | 19       | 19    |
| nm.t.perf_read            | 474      | 481      | 7     |
| nm.t.find_get_context     | 359      | 364      | 5     |
| nm.t.inherit_event        | 364      | 369      | 5     |
| nm.b.nr_task_data_events  | 0        | 4        | 4     |
| nm.b.task_ctx_data_size   | 0        | 4        | 4     |
| nm.t.kzalloc              | 10       | 8        | -2    |
+---------------------------+----------+----------+-------+



Thanks,
Kbuild test robot