All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [lkp] [+1015 bytes kernel size regression] [i386-tinyconfig] [37f7dceb4b] perf: attach/detach PMU specific data
Date: Fri, 10 Jan 2020 22:12:29 +0800	[thread overview]
Message-ID: <20200110141229.v7ernrdjt7cnn7sb@f53c9c00458a> (raw)

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


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

commit: 37f7dceb4b8c6c07560a7a2eebe3000ea63d790f (perf: attach/detach PMU specific data)
url: https://github.com/0day-ci/linux/commits/kan-liang-linux-intel-com/perf-Save-PMU-specific-data-in-task_struct/20200110-042221

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

b69ecfbc: perf: Save PMU specific data in task_struct
37f7dceb: perf: attach/detach PMU specific data

+------------------------------------+----------+----------+-------+
|               symbol               | b69ecfbc | 37f7dceb | delta |
+------------------------------------+----------+----------+-------+
| nm.t.perf_event_alloc              | 1559     | 2071     | 512   |
| bzImage                            | 440272   | 440784   | 512   |
| nm.t._free_event                   | 410      | 547      | 137   |
| nm.T.perf_event_fork               | 20       | 125      | 105   |
| nm.t.alloc_perf_ctx_data           | 0        | 70       | 70    |
| nm.t.detach_task_ctx_data          | 0        | 65       | 65    |
| nm.t.detach_task_ctx_data_sys_wide | 0        | 61       | 61    |
| nm.t.free_perf_ctx_data            | 0        | 19       | 19    |
| nm.T.perf_event_exit_task          | 583      | 596      | 13    |
| nm.T.ring_buffer_put               | 31       | 38       | 7     |
| nm.t.perf_read                     | 474      | 481      | 7     |
| nm.t.put_ctx                       | 62       | 67       | 5     |
| nm.t.find_get_context              | 361      | 366      | 5     |
| nm.t.inherit_event                 | 377      | 382      | 5     |
| nm.b.nr_task_data_sys_wide_events  | 0        | 4        | 4     |
| nm.t.free_perf_ctx_data_rcu        | 0        | 2        | 2     |
| nm.t.kzalloc                       | 10       | 8        | -2    |
+------------------------------------+----------+----------+-------+



Thanks,
Kbuild test robot


                 reply	other threads:[~2020-01-10 14:12 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=20200110141229.v7ernrdjt7cnn7sb@f53c9c00458a \
    --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.