[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a5utg1ec.fsf@all.your.base.are.belong.to.us>
Date: Mon, 14 Aug 2023 16:10:51 +0200
From: Björn Töpel <bjorn@...nel.org>
To: Nam Cao <namcaov@...il.com>
Cc: 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
Subject: Re: test code for kprobe
Nam Cao <namcaov@...il.com> writes:
> On Mon, Aug 14, 2023 at 02:28:11PM +0200, Björn Töpel wrote:
>> 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
>
> Sorry that I wasn't clear with this: I just wanted to show how testing was done.
> This is not meant to be merged.
>
> I do have plans to clean this up and send upstream in the future, but not with
> this patch series.
Please do! A RISC-V specific kprobes test would be nice.
Björn
Powered by blists - more mailing lists