Received-SPF: pass (google.com: domain of linux-kernel+bounces-215326-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>, linux-kernel@vger.kernel.org,
        linux-kbuild@vger.kernel.org, linux-modules@vger.kernel.org,
        linux-trace-kernel@vger.kernel.org
Cc: Masahiro Yamada <masahiroy@kernel.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        Luis Chamberlain <mcgrof@kernel.org>,
        Masami Hiramatsu <mhiramat@kernel.org>,
        Nick Desaulniers <ndesaulniers@google.com>,
        Jiri Olsa <olsajiri@gmail.com>,
        Elena Zannoni <elena.zannoni@oracle.com>
Subject: [PATCH v4 0/3] Generate address range data for built-in modules
Date: Fri, 14 Jun 2024 13:14:25 -0400
Message-ID: <20240614171428.968174-1-kris.van.hees@oracle.com>
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
Precedence: bulk
MIME-Version: 1.0
X-MS-Exchange-AntiSpam-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-MessageData-0: 
	=?us-ascii?Q?wnSrmRKyel8lFNLvduqhIR+5Qx3HUYQQnEm3ZXkrObBRN880XxJsvpBnmbxH?=
 =?us-ascii?Q?nwf4KSm4ggWc5PoruI1s1a2f5aAVTsqATc3oeLe0Im4m6/e0p0OEQNai6Gpl?=
 =?us-ascii?Q?jblHtWpTZSFXhOtn4rlKhrkKsYzPM6pB0mTyNcMIM3k+cfaZlBs0oNFqO07k?=
 =?us-ascii?Q?FcV1HmUC8DZ6HG6t1hAioLCQahNf/4/4Kbike8QYRqJ8ZPWvikOHTFcUi001?=
 =?us-ascii?Q?ZFyZyFeXzkoFIybI/+DfI/xPedbFmsplMiVK0ru48iUg3BEGCLHIi9xg8QGy?=
 =?us-ascii?Q?ryegVQbjiT5Xq5wBimNZISCN0oo2J1wq8A/sdlmX2t6icum/tp3fR45D23j+?=
 =?us-ascii?Q?mkKvyynubIiF63/SC/jiqYfoXksqCuhdWXr7fE+RXEBGaIlmHboyOrDTn2mZ?=
 =?us-ascii?Q?VjxV5SqeQp6D1nL1F1znLRZByYLl4ZMHlKMBk7he1sN+GP/S36z9UGdncCno?=
 =?us-ascii?Q?HCwbu5y3PN+l2NbXGbEbB6IZDLBQAbXCXsE2jCy1AFynm+Bc5qTunu3j6dCs?=
 =?us-ascii?Q?URts4z8rB154Uw21G/XRCkq6Uz6NX6KeTM/c9WtvVx+sf6scGoSvY27IaI5+?=
 =?us-ascii?Q?/Vj/aixD8zQjqxiyIwe/yeolYS0jz5qSD/luu3ixrFIwTd8lvf99TV0JXR9f?=
 =?us-ascii?Q?3VMeUzA6QeAViDzd8E1WyAp7XcR4x9tDwYAuF/VKILK9EhPTUm+Abua4J/nZ?=
 =?us-ascii?Q?TkaFoBjb9iA/ZXVOMYud8lJXOWEo0MaVFsRFyh9cr9+tiq2Nutd0nBTapIRF?=
 =?us-ascii?Q?e084eepkmT2rNW4DR5D2Au0yV5mCU7QmYLQ2SANHHnJqlfAaO83q66GxGRq7?=
 =?us-ascii?Q?T06yA1jxtmMeY0w0JsUR1qTv8Kf1+JHIMRsId4S4cZOA9BY7x9bAJE5aaJIz?=
 =?us-ascii?Q?a+s2Vp0Vc0nTuEHrpPcRmQ0WptL9Yw7LXFBpRDFXqkUIxEVNJGpFOtbpXZxN?=
 =?us-ascii?Q?rRzmi4MvvFJSfXcYy/PXfXrx0IwLpoMGmlCatonrNL7OjPGnDOapT6joRjZj?=
 =?us-ascii?Q?7BtCsCQ6Zs7/ObCQx9T4UXmG3fyUWGi8V0c4sjCoAV8zim0pM9e6spM9+hPP?=
 =?us-ascii?Q?c6hY7he15sa73Z8ZCLMYQz5m4pFlWKcWlm4WEECoG1QDJmAkV9jg2cgze0uy?=
 =?us-ascii?Q?wVsGxDOjdlkYmacFHHNzKTXEyUfhx/njP/3ke2zt+CFpkxpVoT46PLLf/EuG?=
 =?us-ascii?Q?xwltRHywjQjOWXwr17/L591obHGnPE8FZmov5XVa2Hl0EkYzih//brp7PDHL?=
 =?us-ascii?Q?uJq4Dzei8QRUu4Ui+vEIBB8/dN545QkTUx72LOaP39lQwBH4epe28ushI3qc?=
 =?us-ascii?Q?AkQiX0GHzsjxjg0JUHlvvX/KXQ/zhR08Ya7pkNbSGC6aXhMW7uv4vx/3pQJy?=
 =?us-ascii?Q?/McotEGpjTWBaeprCasLQDe2Rhar4cbMXFjTT0qtdqL7IFQ9+YA5t6/VEwhg?=
 =?us-ascii?Q?Awzj+VLK1Z/xRpGrvo8THMplvgeBh3fr+1R5iQrU6bYdqZb4PJGxHq3SNcVr?=
 =?us-ascii?Q?zBV53uty0vJ3PpO7ZLiXDMapM2Hk1mj2ktdqOGuROOH1bIF47e0eOaJSoYev?=
 =?us-ascii?Q?THwq5m1R6lTCoi9j1ZQ6fL9yT9y4A5FNTtL+YQ+4oQfudkTE5V9CZMsSqEH5?=
 =?us-ascii?Q?TQ=3D=3D?=
X-MS-Exchange-AntiSpam-ExternalHop-MessageData-ChunkCount: 1
X-MS-Exchange-AntiSpam-ExternalHop-MessageData-0: 
	Q1dkl50D84E3sQ/pIpkQFPNJgvdxAA8hYSIbPpBtQEc44lU3FAlt1OV3Y1fZcXU1WD6ngKQybbF8yh3DQ1nUudjCv1aG5HtCPk0QOOaI+PQ+vELCUME/VtCRXwyjVD/zxGlZozsZQxOrT8xXG9UbuQOJSwv5yA/u24wpR68GzgOGRmpMg3QAArr6IPFcGmREbsuf63if1TwPHE/hrzMOKvmDg6GMxGpdAFVzKF3Z/fMpJ/CIM5VdRxLW1lYqub8OZLfWHuQjAhYqewxGLzDPLNzlr616w88o4bEPFFaM0Q+VsUz/YYvRBABj47siPFd5rp++cQMn2SDE9SgSqD0ztCBjX0flSXzeKUoZbpC2E37jFNiavOJPhS7QyHI8X+U3lL8st8JyG/RaeCvHcTJrG11T5AvLrxYJltM979L06JhMhSEaYSOLvMMb8u2up4cwtQmY2WQkm9XEeF7ncI8dWE1rhm3rjUqaKYQxxJlCvjn83Tqx4keyAEh6c5dHXyutfbzXQwKdELCSg0zUx9gIZ5cwzRLqq5yYpP8IUHhmgW1erxoSzrs8MwPFR0AtfY4vr+w3bCiPv0KilRB6PBvdJejPAyF763he3jQcqtbP0XU=
X-OriginatorOrg: oracle.com
X-MS-Exchange-CrossTenant-Network-Message-Id: e127c39a-849f-48f0-32c7-08dc8c958dd1
X-MS-Exchange-CrossTenant-AuthSource: SN7PR10MB6287.namprd10.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Jun 2024 17:15:13.7916
 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 4e2c6054-71cb-48f1-bd6c-3a9705aca71b
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: hJav076B6SwZ70QcRfLuOKaH75qKClhPxcSFMSJz2uvGu5TflYEhdBb+aP+ljVWM8HCvRBr89WM2fbbQem9RXc+cnVtDVX20jwCtusYJJVE=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM4PR10MB7404
X-Proofpoint-Virus-Version: vendor=baseguard
 engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.28.16
 definitions=2024-06-14_15,2024-06-14_03,2024-05-17_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxlogscore=999 adultscore=0
 phishscore=0 suspectscore=0 malwarescore=0 mlxscore=0 spamscore=0
 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1
 engine=8.12.0-2405010000 definitions=main-2406140118
X-Proofpoint-GUID: PeRYQPy_idNK0TnRsnZ-qCPbibuH2Izl
X-Proofpoint-ORIG-GUID: PeRYQPy_idNK0TnRsnZ-qCPbibuH2Izl

Especially for tracing applications, it is convenient to be able to
refer to a symbol using a <module name, symbol name> pair and to be able
to translate an address into a <nodule mname, symbol name> pair.  But
that does not work if the module is built into the kernel because the
object files that comprise the built-in module implementation are simply
linked into the kernel image along with all other kernel object files.

This is especially visible when providing tracing scripts for support
purposes, where the developer of the script targets a particular kernel
version, but does not have control over whether the target system has
a particular module as loadable module or built-in module.  When tracing
symbols within a module, referring them by <module name, symbol name>
pairs is both convenient and aids symbol lookup.  But that naming will
not work if the module name information is lost if the module is built
into the kernel on the target system.

Earlier work addressing this loss of information for built-in modules
involved adding module name information to the kallsyms data, but that
required more invasive code in the kernel proper.  This work never did
get merged into the kernel tree.

All that is really needed is knowing whether a given address belongs to
a particular module (or multiple modules if they share an object file).
Or in other words, whether that address falls within an address range
that is associated with one or more modules.

Objects can be identified as belonging to a particular module (or
modules) based on defines that are passed as flags to their respective
compilation commands.  The data found in modules.builtin is used to
determine what modules are built into the kernel proper.  Then,
vmlinux.o.map and vmlinux.map can be parsed in a single pass to generate
a modules.buitin.ranges file with offset range information (relative to
the base address of the associated section) for built-in modules.  This
file gets installed along with the other modules.builtin.* files.

The impact on the kernel build is minimal because everything is done
using a single-pass AWK script.  The generated data size is minimal as
well, (depending on the exact kernel configuration) usually in the range
of 500-700 lines, with a file size of 20-40KB (if all modules are built
in, the file contains about 8000 lines, with a file size of about 285KB).

Changes since v3:
 - Consolidated patches 2 through 5 into a single patch
 - Move CONFIG_BUILTIN_MODULE_RANGES to Kconfig.debug
 - Make CONFIG_BUILTIN_MODULE_RANGES select CONFIG_VMLINUX_MAP
 - Disable CONFIG_BUILTIN_MODULE_RANGES if CONFIG_LTO_CLANG_(FULL|THIN)=y
 - Support LLVM (lld) compiles in generate_builtin_ranges.awk
 - Support CONFIG_LD_DEAD_CODE_DATA_ELIMINATION=y
 - Only install modules.builtin.ranges if CONFIG_BUILTIN_MODULE_RANGES=y

Changes since v2:
 - Switched from using modules.builtin.objs to parsing .*.cmd files
 - Add explicit dependency on FTRACE for CONFIG_BUILTIN_MODULE_RANGES
 - 1st arg to generate_builtin_ranges.awk is now modules.builtin.modinfo
 - Parse data from .*.cmd in generate_builtin_ranges.awk
 - Use $(real-prereqs) rather than $(filter-out ...)
 - Include modules.builtin.ranges in modules install target

Changes since v1:
 - Renamed CONFIG_BUILTIN_RANGES to CONFIG_BUILTIN_MODULE_RANGES
 - Moved the config option to the tracers section
 - 2nd arg to generate_builtin_ranges.awk should be vmlinux.map

Kris Van Hees (5):
  trace: add CONFIG_BUILTIN_MODULE_RANGES option
  kbuild: generate a linker map for vmlinux.o
  module: script to generate offset ranges for builtin modules
  kbuild: generate modules.builtin.ranges when linking the kernel
  module: add install target for modules.builtin.ranges

Luis Chamberlain (1):
  kbuild: add modules.builtin.objs

 .gitignore                          |   2 +-
 Documentation/dontdiff              |   2 +-
 Documentation/kbuild/kbuild.rst     |   5 ++
 Makefile                            |   8 +-
 include/linux/module.h              |   4 +-
 kernel/trace/Kconfig                |  17 ++++
 scripts/Makefile.lib                |   5 +-
 scripts/Makefile.modinst            |  11 ++-
 scripts/Makefile.vmlinux            |  17 ++++
 scripts/Makefile.vmlinux_o          |  18 ++++-
 scripts/generate_builtin_ranges.awk | 149 ++++++++++++++++++++++++++++++++++++
 11 files changed, 228 insertions(+), 10 deletions(-)
 create mode 100755 scripts/generate_builtin_ranges.awk


base-commit: dd5a440a31fae6e459c0d6271dddd62825505361
-- 
2.42.0