From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [lkp] [+794 bytes kernel size regression] [i386-tinyconfig] [b473cfff35] perf: Allocate space in task_struct for pmu specific data
Date: Wed, 23 Oct 2019 06:35:04 +0800 [thread overview]
Message-ID: <5daf8418.Sc120NsHMp7AG6dh%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
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
reply other threads:[~2019-10-22 22:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5daf8418.Sc120NsHMp7AG6dh%lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.