From: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
To: Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Johannes Berg <johannes@sipsolutions.net>,
Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: linux-um@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
"Nam Cao" <namcao@linutronix.de>,
"Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Subject: [PATCH 0/2] um/ptrace: Implement HAVE_SYSCALL_TRACEPOINTS
Date: Thu, 03 Jul 2025 14:38:53 +0200 [thread overview]
Message-ID: <20250703-uml-have_syscall_tracepoints-v1-0-23c1d3808578@linutronix.de> (raw)
Implement syscall tracepoints through the generic tracing infrastructure.
We want to use this to run realtime validation monitors [0] inside UML,
to test applications for PREEMPT_RT compliance.
[0] https://lore.kernel.org/lkml/cover.1749547399.git.namcao@linutronix.de/
Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
---
Thomas Weißschuh (2):
um/x86: Add system call table to header file
um/ptrace: Implement HAVE_SYSCALL_TRACEPOINTS
arch/um/Kconfig | 1 +
arch/um/include/asm/thread_info.h | 2 ++
arch/um/kernel/ptrace.c | 9 +++++++++
arch/x86/um/asm/syscall.h | 2 ++
4 files changed, 14 insertions(+)
---
base-commit: 19272b37aa4f83ca52bdf9c16d5d81bdd1354494
change-id: 20250702-uml-have_syscall_tracepoints-9f4d182fc308
Best regards,
--
Thomas Weißschuh <thomas.weissschuh@linutronix.de>
next reply other threads:[~2025-07-03 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 12:38 Thomas Weißschuh [this message]
2025-07-03 12:38 ` [PATCH 1/2] um/x86: Add system call table to header file Thomas Weißschuh
2025-07-03 12:38 ` [PATCH 2/2] um/ptrace: Implement HAVE_SYSCALL_TRACEPOINTS Thomas Weißschuh
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=20250703-uml-have_syscall_tracepoints-v1-0-23c1d3808578@linutronix.de \
--to=thomas.weissschuh@linutronix.de \
--cc=anton.ivanov@cambridgegreys.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namcao@linutronix.de \
--cc=richard@nod.at \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).