From: Tiezhu Yang <yangtiezhu@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Lisa Robinson <lisa@bytefly.space>, WANG Rui <r@hev.cc>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] Fix ftrace and kprobes issues for LoongArch
Date: Fri, 22 May 2026 10:16:55 +0800 [thread overview]
Message-ID: <c4e4cd61-b909-dfb8-c265-437b86d6c2e7@loongson.cn> (raw)
In-Reply-To: <CAAhV-H57233=4Sr+yRDsxp6WaTiDj3OdBqG34WE5dR+HLE_5mg@mail.gmail.com>
On 2026/5/21 下午8:52, Huacai Chen wrote:
> On Thu, May 21, 2026 at 10:37 AM Tiezhu Yang <yangtiezhu@loongson.cn> wrote:
...
> OK, but I want to remove preempt_enable_no_resched() in Patch#4
> because all other architectures have no.
As the commit message said, this is to balance the preemption count.
We don't want to be preempted for the entire duration of kprobe
processing, preempt_disable() is called at the start of
kprobe_breakpoint_handler(), so preempt_enable_no_resched()
should also be called at each exit path.
So, it should keep the code as is.
Thanks,
Tiezhu
next prev parent reply other threads:[~2026-05-22 2:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 8:20 Tiezhu Yang
2026-05-12 8:20 ` [PATCH v1 1/4] LoongArch: ftrace: Fix stale per-CPU kprobe state after task migration Tiezhu Yang
2026-05-12 8:20 ` [PATCH v1 2/4] LoongArch: kprobes: Use larch_insn_text_copy() to patch instructions Tiezhu Yang
2026-05-12 8:20 ` [PATCH v1 3/4] LoongArch: kprobes: Fix single-stepping instruction slot preparation Tiezhu Yang
2026-05-13 6:15 ` Lisa Robinson
2026-05-14 13:20 ` WANG Rui
2026-05-12 8:20 ` [PATCH v1 4/4] LoongArch: kprobes: Fix handling of fatal unrecoverable recursions Tiezhu Yang
2026-05-15 2:52 ` [PATCH v1 0/4] Fix ftrace and kprobes issues for LoongArch Tiezhu Yang
2026-05-15 4:29 ` Huacai Chen
2026-05-20 7:58 ` Huacai Chen
2026-05-21 2:37 ` Tiezhu Yang
2026-05-21 12:52 ` Huacai Chen
2026-05-22 2:16 ` Tiezhu Yang [this message]
2026-05-22 2:40 ` Huacai Chen
2026-05-22 3:02 ` Tiezhu Yang
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=c4e4cd61-b909-dfb8-c265-437b86d6c2e7@loongson.cn \
--to=yangtiezhu@loongson.cn \
--cc=chenhuacai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lisa@bytefly.space \
--cc=loongarch@lists.linux.dev \
--cc=r@hev.cc \
/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®