[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230525210040.3637-1-namit@vmware.com>
Date: Thu, 25 May 2023 14:00:37 -0700
From: Nadav Amit <nadav.amit@...il.com>
To: Steven Rostedt <rostedt@...dmis.org>,
"Arnd Bergmann" <arnd@...db.de>,
"Thomas Gleixner" <tglx@...utronix.de>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-ia64@...r.kernel.org, linux-um@...ts.infradead.org,
Linux-Arch <linux-arch@...r.kernel.org>, linux-mm@...ck.org,
"Andy Lutomirski" <luto@...nel.org>,
"Ingo Molnar" <mingo@...hat.com>,
"Dave Hansen" <dave.hansen@...ux.intel.com>,
"Borislav Petkov" <bp@...en8.de>, x86@...nel.org,
Peter Zijlstra <peterz@...radead.org>,
Nadav Amit <namit@...are.com>
Subject: [PATCH v2 0/3] kprobes: notrace enhancements
From: Nadav Amit <namit@...are.com>
There are inconsistencies and some issues in marking functions as
notrace. On one hand, all inline functions are marked as "notrace" and
some libraries cannot be traced. As more users and tools try to make use
of the tracing functionality, it is beneficial to allow their tracing as
possible.
At the same time, some functions should not be traced but are not marked
as notrace.
These patch address issues that I encountered during work on an
automatic tracing tool.
---
v1->v2:
* Add find_bit to tracable libraries
* Improve the change log to explain the reasons for inline->notrace
* Switch the order of patch 2 and patch 3
Nadav Amit (3):
kprobes: Mark descendents of core_kernel_text as notrace
compiler: inline does not imply notrace
lib: Allow traceing of usercopy, xarray, iov_iter, find_bit
arch/arm/kernel/process.c | 2 +-
arch/ia64/mm/init.c | 2 +-
arch/x86/entry/vsyscall/vsyscall_64.c | 2 +-
arch/x86/um/mem_32.c | 2 +-
include/asm-generic/sections.h | 6 +++---
include/linux/compiler_types.h | 2 +-
include/linux/kallsyms.h | 6 +++---
include/linux/mm.h | 2 +-
lib/Makefile | 5 +++++
9 files changed, 17 insertions(+), 12 deletions(-)
--
2.25.1
Powered by blists - more mailing lists