[lkp] [+908 bytes kernel size regression] [i386-tinyconfig] [47f94ef0a6] perf: Init/fini PMU specific data

[lkp] [+908 bytes kernel size regression] [i386-tinyconfig] [47f94ef0a6] perf: Init/fini PMU specific data

[kbuild test robot]

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]


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

commit: 47f94ef0a67522f300b330632670d6cd5c560a84 (perf: Init/fini PMU specific data)
 

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

9d010201: perf: Helpers for alloc/init/fini PMU specific data
47f94ef0: perf: Init/fini PMU specific data

+--------------------------------+----------+----------+-------+
|             symbol             | 9d010201 | 47f94ef0 | delta |
+--------------------------------+----------+----------+-------+
| nm.t.perf_event_alloc          | 1595     | 2058     | 463   |
| bzImage                        | 439840   | 440224   | 384   |
| nm.t._free_event               | 410      | 560      | 150   |
| nm.t.__alloc_task_ctx_data_rcu | 0        | 107      | 107   |
| nm.t.fini_task_ctx_data_rcu    | 0        | 78       | 78    |
| nm.T.perf_event_fork           | 20       | 79       | 59    |
| nm.t.free_perf_ctx_data        | 0        | 19       | 19    |
| nm.T.perf_event_exit_task      | 583      | 596      | 13    |
| nm.t.perf_read                 | 474      | 481      | 7     |
| nm.t.find_get_context          | 359      | 364      | 5     |
| nm.t.inherit_event             | 374      | 379      | 5     |
| nm.b.nr_task_data_events       | 0        | 4        | 4     |
| nm.t.kzalloc                   | 10       | 8        | -2    |
+--------------------------------+----------+----------+-------+



Thanks,
Kbuild test robot