From: Hengqi Chen <chenhengqi@outlook.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>
Cc: loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v3 0/6] Add uprobes support for LoongArch
Date: Thu, 4 May 2023 10:03:09 +0800 [thread overview]
Message-ID: <SY4P282MB3518B7072E26AE054372D818C06D9@SY4P282MB3518.AUSP282.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <1681898221-27828-1-git-send-email-yangtiezhu@loongson.cn>
On 2023/4/19 17:56, Tiezhu Yang wrote:
> v3:
> -- Check atomic instructions in insns_not_supported()
> -- Remove five DIE_* definitions in kdebug.h
>
> v2:
> -- Move the functions to inst.c in patch #1
> -- Pass around union for insns_not_supported(),
> insns_need_simulation() and arch_simulate_insn()
>
> v1:
> -- Split the RFC patch #2 into two patches
> -- Use larch_insn_gen_break() to generate break insns
> for kprobes and uprobes
> -- Pass around instruction word instead of union for
> insns_not_supported(), insns_need_simulation() and
> arch_simulate_insn() to avoid type conversion for callers
> -- Add a simple test case for uprobes in the commit message
>
> Tiezhu Yang (6):
> LoongArch: Move three functions from kprobes.c to inst.c
> LoongArch: Add larch_insn_gen_break() to generate break insns
> LoongArch: Use larch_insn_gen_break() for kprobes
> LoongArch: Add uprobes support
> LoongArch: Check atomic instructions in insns_not_supported()
> LoongArch: Remove five DIE_* definitions in kdebug.h
>
> arch/loongarch/Kconfig | 3 +
> arch/loongarch/include/asm/inst.h | 42 ++++++++++
> arch/loongarch/include/asm/kdebug.h | 5 --
> arch/loongarch/include/asm/kprobes.h | 2 +-
> arch/loongarch/include/asm/uprobes.h | 36 +++++++++
> arch/loongarch/kernel/Makefile | 1 +
> arch/loongarch/kernel/inst.c | 54 +++++++++++++
> arch/loongarch/kernel/kprobes.c | 75 ++++--------------
> arch/loongarch/kernel/traps.c | 9 +--
> arch/loongarch/kernel/uprobes.c | 143 +++++++++++++++++++++++++++++++++++
> 10 files changed, 298 insertions(+), 72 deletions(-)
> create mode 100644 arch/loongarch/include/asm/uprobes.h
> create mode 100644 arch/loongarch/kernel/uprobes.c
>
For the series,
Tested-by: Hengqi Chen <hengqi.chen@gmail.com>
prev parent reply other threads:[~2023-05-04 2:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 9:56 Tiezhu Yang
2023-04-19 9:56 ` [PATCH v3 1/6] LoongArch: Move three functions from kprobes.c to inst.c Tiezhu Yang
2023-04-19 9:56 ` [PATCH v3 2/6] LoongArch: Add larch_insn_gen_break() to generate break insns Tiezhu Yang
2023-04-19 9:56 ` [PATCH v3 3/6] LoongArch: Use larch_insn_gen_break() for kprobes Tiezhu Yang
2023-04-19 9:56 ` [PATCH v3 4/6] LoongArch: Add uprobes support Tiezhu Yang
2023-04-23 13:12 ` Huacai Chen
2023-04-24 1:19 ` Tiezhu Yang
2023-04-19 9:57 ` [PATCH v3 5/6] LoongArch: Check atomic instructions in insns_not_supported() Tiezhu Yang
2023-04-19 9:57 ` [PATCH v3 6/6] LoongArch: Remove five DIE_* definitions in kdebug.h Tiezhu Yang
2023-04-28 11:05 ` [PATCH v3 0/6] Add uprobes support for LoongArch Jeff Xie
2023-05-04 2:03 ` Hengqi Chen [this message]
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=SY4P282MB3518B7072E26AE054372D818C06D9@SY4P282MB3518.AUSP282.PROD.OUTLOOK.COM \
--to=chenhengqi@outlook.com \
--cc=chenhuacai@kernel.org \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®