[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a63ncr1y.fsf@esperi.org.uk>
Date: Fri, 16 Dec 2022 15:21:45 +0000
From: Nick Alcock <nick.alcock@...cle.com>
To: mcgrof@...nel.org, masahiroy@...nel.org
Cc: linux-modules@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
linux-kernel@...r.kernel.org, arnd@...db.de,
akpm@...ux-foundation.org, eugene.loh@...cle.com,
kris.van.hees@...cle.com
Subject: Re: [PING] [PATCH modules-next v10 00/13] kallsyms: reliable
symbol->address lookup with /proc/kallmodsyms
(hand-hacked reply: hope it threads properly)
[...]
> A kernel tree containing this series alone:
> https://github.com/oracle/dtrace-linux-kernel kallmodsyms/6.1-rc4-modules-next
[...]
> Nick Alcock (12):
> kbuild: bring back tristate.conf
> kbuild: add tristate checker
> kbuild: fix up substitutions in makefiles to allow for tristate
> checker
> kbuild: remove MODULE_LICENSE/AUTHOR/DESCRIPTION in non-modules
> build: add a simple iterator over modules.builtin.objs
> kbuild: generate an address ranges map at vmlinux link time
> kbuild: make address ranges map work with IBT
> kallsyms: introduce sections needed to map symbols to built-in modules
> kallsyms: optimize .kallsyms_modules*
> kallsyms: distinguish text symbols fully using object file names
> kallsyms: add /proc/kallmodsyms for text symbol disambiguation
> perf: proof-of-concept kallmodsyms support
It's been a couple of weeks, so a gentle ping seems in order :) (I can
resend if people need it, but I suspect everyone interested has it
already.)
Powered by blists - more mailing lists