From: kernel test robot <lkp@intel.com>
To: Gregory Price <gourry.memverge@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, lkp@intel.com,
Josh Triplett <josh@joshtriplett.org>
Subject: [lkp] [+258 bytes kernel size regression] [i386-tinyconfig] [39a1aa674d] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD
Date: Thu, 2 Mar 2023 06:08:25 +0800 [thread overview]
Message-ID: <Y//M2bLFnYdftzuz@8d190a1611c4> (raw)
In-Reply-To: <20230301205843.2164-3-gregory.price@memverge.com>
FYI, we noticed a +258 bytes kernel size regression due to commit:
commit: 39a1aa674dbf23f8f44af1eb2bd1d01a9531de8e (ptrace,syscall_user_dispatch: checkpoint/restore support for SUD)
url: https://github.com/intel-lab-lkp/linux/commits/Gregory-Price/syscall_user_dispatch-helper-function-to-operate-on-given-task/20230302-050205
base: https://git.kernel.org/cgit/linux/kernel/git/shuah/linux-kselftest.git next
patch link: https://lore.kernel.org/all/20230301205843.2164-3-gregory.price@memverge.com/
patch subject: [PATCH v13 2/3] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD
Details as below (size data is obtained by `nm --size-sort vmlinux`):
43d29eea: syscall_user_dispatch: helper function to operate on given task
39a1aa67: ptrace,syscall_user_dispatch: checkpoint/restore support for SUD
+---------------------------------------+----------+----------+-------+
| symbol | 43d29eea | 39a1aa67 | delta |
+---------------------------------------+----------+----------+-------+
| bzImage | 495936 | 496064 | 128 |
| nm.t.task_set_syscall_user_dispatch | 0 | 127 | 127 |
| nm.T.syscall_user_dispatch_get_config | 0 | 117 | 117 |
| nm.T.syscall_user_dispatch_set_config | 0 | 73 | 73 |
| nm.T.ptrace_request | 1186 | 1228 | 42 |
| nm.D.linux_banner | 165 | 166 | 1 |
| nm.T.set_syscall_user_dispatch | 128 | 26 | -102 |
+---------------------------------------+----------+----------+-------+
Thanks
next prev parent reply other threads:[~2023-03-01 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 20:58 [PATCH v13 0/3] Checkpoint Support for Syscall User Dispatch Gregory Price
2023-03-01 20:58 ` [PATCH v13 1/3] syscall_user_dispatch: helper function to operate on given task Gregory Price
2023-03-06 18:04 ` Oleg Nesterov
2023-03-21 15:41 ` Thomas Gleixner
2023-03-21 16:55 ` Gregory Price
2023-03-21 19:46 ` Thomas Gleixner
2023-03-21 21:12 ` Gregory Price
2023-03-01 20:58 ` [PATCH v13 2/3] ptrace,syscall_user_dispatch: checkpoint/restore support for SUD Gregory Price
2023-03-01 22:08 ` kernel test robot [this message]
2023-03-06 18:04 ` Oleg Nesterov
2023-03-01 20:58 ` [PATCH v13 3/3] selftest,ptrace: Add selftest for syscall user dispatch config api Gregory Price
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=Y//M2bLFnYdftzuz@8d190a1611c4 \
--to=lkp@intel.com \
--cc=gourry.memverge@gmail.com \
--cc=josh@joshtriplett.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.