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] [+83 bytes kernel size regression] [i386-tinyconfig] [97192c6c04] sched/core: Add function to sample state of locked-down task
Date: Fri, 17 Apr 2020 10:49:49 +0800	[thread overview]
Message-ID: <20200417024949.GA26326@shao2-debian> (raw)

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

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

commit: 97192c6c046907e58e6cdb958d0c3d7e5d7c289d (sched/core: Add function to sample state of locked-down task)
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2020.04.13b

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

d9899f93: MAINTAINERS: Update maintainers for new Documentaion/litmus-tests/
97192c6c: sched/core: Add function to sample state of locked-down task

+-------------------------------------+----------+----------+-------+
|               symbol                | d9899f93 | 97192c6c | delta |
+-------------------------------------+----------+----------+-------+
| bzImage                             | 439232   | 439392   | 160   |
| nm.T.try_invoke_on_locked_down_task | 0        | 83       | 83    |
+-------------------------------------+----------+----------+-------+



Thanks,
Kbuild test robot

             reply	other threads:[~2020-04-17  2:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17  2:49 kbuild test robot [this message]
2020-04-17  3:03 ` [lkp] [+83 bytes kernel size regression] [i386-tinyconfig] [97192c6c04] sched/core: Add function to sample state of locked-down task Paul E. McKenney
2020-04-17  3:05   ` Rong Chen
2020-04-17  3:23     ` Paul E. McKenney

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=20200417024949.GA26326@shao2-debian \
    --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.