[PATCH 1/2] selftests/dmabuf-heap: conform test to TAP format output

Conform the layout, informational and status messages to TAP. No functional change is intended other than the layout of output messages. Signed-off-by: Muhammad Usama Anjum --- .../selftests/dmabuf-heaps/dmabuf-heap.c | 194 +++--- 1 file changed, 77 insertions(+), 117 deletions

Re: [PATCH v2] selftests/ftrace: Limit length in subsystem-enable tests

On Mon, 26 Feb 2024 11:18:16 +0800 Yuanhe Shu wrote: > While sched* events being traced and sched* events continuously happen, > "[xx] event tracing - enable/disable with subsystem level files" would > not stop as on some slower systems it seems to take forever. > Select the first 100 lines of ou

Re: [PATCH v5 11/12] KVM: riscv: selftests: Change vcpu_has_ext to a common function

On Mon, Feb 26, 2024 at 1:20 PM Anup Patel wrote: > > On Wed, Feb 21, 2024 at 2:07 PM Atish Patra wrote: > > > > On 2/20/24 18:13, Haibo Xu wrote: > > > On Wed, Feb 21, 2024 at 7:03 AM Atish Patra wrote: > > >> > > >> On Mon, Jan 22, 2024 at 1:48 AM Haibo Xu wrote: > > >>> > > >>> Move vcpu_has

Re: [PATCH v5 11/12] KVM: riscv: selftests: Change vcpu_has_ext to a common function

On Wed, Feb 21, 2024 at 2:07 PM Atish Patra wrote: > > On 2/20/24 18:13, Haibo Xu wrote: > > On Wed, Feb 21, 2024 at 7:03 AM Atish Patra wrote: > >> > >> On Mon, Jan 22, 2024 at 1:48 AM Haibo Xu wrote: > >>> > >>> Move vcpu_has_ext to the processor.c and rename it to __vcpu_has_ext > >>> so that

[PATCH v2 7/7] Documentation: tracing: Add entry argument access at function exit

From: Masami Hiramatsu (Google) Add a notes about the entry argument access at function exit probes for kprobes and fprobe trace event. Signed-off-by: Masami Hiramatsu (Google) --- Documentation/trace/fprobetrace.rst |7 +++ Documentation/trace/kprobetrace.rst |7 +++ 2 files c

[PATCH v2 6/7] selftests/ftrace: Add test cases for entry args at function exit

From: Masami Hiramatsu (Google) Add kretprobe and function exit probe test cases for checking whether those can access entry arguments at function exit correctly. Signed-off-by: Masami Hiramatsu (Google) --- .../ftrace/test.d/dynevent/fprobe_entry_arg.tc | 18 ++ .../ftra

[PATCH v2 5/7] tracing/probes: Support $argN in return probe (kprobe and fprobe)

From: Masami Hiramatsu (Google) Support accessing $argN in the return probe events. This will help users to record entry data in function return (exit) event for simplfing the function entry/exit information in one event, and record the result values (e.g. allocated object/initialized object) at

[PATCH v2 4/7] tracing: Remove redundant #else block for BTF args from README

From: Masami Hiramatsu (Google) Remove redundant #else block for BTF args from README message. This is a cleanup, so no change on the message. Signed-off-by: Masami Hiramatsu (Google) --- kernel/trace/trace.c |4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/kernel/trac

[PATCH v2 3/7] tracing/probes: cleanup: Set trace_probe::nr_args at trace_probe_init

From: Masami Hiramatsu (Google) Instead of incrementing the trace_probe::nr_args, init it at trace_probe_init(). This is a cleanup, so the behavior is not changed. Signed-off-by: Masami Hiramatsu (Google) --- kernel/trace/trace_eprobe.c |2 +- kernel/trace/trace_probe.c | 10 ++

[PATCH v2 2/7] tracing/probes: Cleanup probe argument parser

From: Masami Hiramatsu (Google) Cleanup traceprobe_parse_probe_arg_body() to split out the type parser and post-processing part of fetch_insn. This makes no functional change. Signed-off-by: Masami Hiramatsu (Google) --- kernel/trace/trace_probe.c | 230 ++-

[PATCH v2 1/7] tracing/fprobe-event: cleanup: Fix a wrong comment in fprobe event

From: Masami Hiramatsu (Google) Despite the fprobe event, "Kretprobe" was commented. So fix it. Signed-off-by: Masami Hiramatsu (Google) --- kernel/trace/trace_fprobe.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/trace/trace_fprobe.c b/kernel/trace/trace_fpro

[PATCH v2 0/7] tracing/probes: Support function parameter access from return probe

Hi, Here is version 2 series of patches to support accessing function entry data from function *return* probes (including kretprobe and fprobe-exit event). In this version, I added another cleanup [4/7], updated README[5/7], added testcases[6/7] and updated document[7/7]. This allows us to acces

[PATCH v2] selftests/ftrace: Limit length in subsystem-enable tests

While sched* events being traced and sched* events continuously happen, "[xx] event tracing - enable/disable with subsystem level files" would not stop as on some slower systems it seems to take forever. Select the first 100 lines of output would be enough to judge whether there are more than 3 typ

Re: [PATCH] selftests/ftrace: Limit length in subsystem-enable tests

On Thu, 22 Feb 2024 20:14:56 +0800 Yuanhe Shu wrote: > > > On 2024/2/5 21:21, Steven Rostedt wrote: > > On Mon, 5 Feb 2024 21:12:33 +0800 > > Yuanhe Shu wrote: > > > >> While sched* events being traced and sched* events continuously happen, > >> "[xx] event tracing - enable/disable with subs

[RFC PATCH] selftest/powerpc: Add rule file to address sub-folder test fail

When running `make -C powerpc/pmu run_tests` from top level selftests directory, currently this error is being reported make: Entering directory '/home/maddy/linux/tools/testing/selftests/powerpc/pmu' Makefile:40: warning: overriding recipe for target 'emit_tests' ../../lib.mk:111: warning: ignori