[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87il9hg65g.fsf@all.your.base.are.belong.to.us>
Date: Mon, 14 Aug 2023 14:28:11 +0200
From: Björn Töpel <bjorn@...nel.org>
To: Nam Cao <namcaov@...il.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: Nam Cao <namcaov@...il.com>
Subject: Re: test code for kprobe
Nam Cao <namcaov@...il.com> writes:
A RISC-V specific kprobes test -- much welcome!
Please add a proper commit message here.
> ---
> drivers/test_kprobe/Makefile | 3 +
> drivers/test_kprobe/test_kprobe.c | 265 ++++++++++++++++++++++++++++++
> 2 files changed, 268 insertions(+)
> create mode 100644 drivers/test_kprobe/Makefile
> create mode 100644 drivers/test_kprobe/test_kprobe.c
>
> diff --git a/drivers/test_kprobe/Makefile b/drivers/test_kprobe/Makefile
Architecture specific test code usually reside in "arch/$ARCH"
(arch/riscv), and is part of Kconfig.debug.
Have a look at:
* grep for ARM_KPROBES_TEST in arch/arm
* grep for KPROBES_SANITY_TEST, and in arch/powerpc grep
test_emulate_step
* grep S390_KPROBES_SANITY_TEST
Björn
Powered by blists - more mailing lists