From: Yipeng Zou <zouyipeng@huawei.com>
To: <x86@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-csky@vger.kernel.org>,
<linux-riscv@lists.infradead.org>,
<linux-perf-users@vger.kernel.org>, <linux-s390@vger.kernel.org>,
<guoren@kernel.org>, <paul.walmsley@sifive.com>,
<palmer@dabbelt.com>, <hca@linux.ibm.com>, <gor@linux.ibm.com>,
<borntraeger@linux.ibm.com>, <dave.hansen@linux.intel.com>,
<hpa@zytor.com>, <naveen.n.rao@linux.ibm.com>,
<anil.s.keshavamurthy@intel.com>, <mhiramat@kernel.org>,
<namit@vmware.com>, <catalin.marinas@arm.com>,
<peterz@infradead.org>, <mark.rutland@arm.com>
Cc: <liaochang1@huawei.com>, <chris.zjh@huawei.com>, <zouyipeng@huawei.com>
Subject: [PATCH 0/2] make weak attributes in {k,u}probes
Date: Sat, 17 Sep 2022 09:55:20 +0800 [thread overview]
Message-ID: <20220917015522.44583-1-zouyipeng@huawei.com> (raw)
We have some function implementation under some arch does nothing.
We can mark it with weak attributes to improve.
1. arch_init_kprobes in kprobes
2. arch_uprobe_exception_notify in uprobes
Yipeng Zou (2):
kprobes: make arch_init_kprobes as weak
uprobes: make arch_uprobe_exception_notify as weak
arch/arm/probes/uprobes/core.c | 6 ------
arch/arm64/kernel/probes/uprobes.c | 6 ------
arch/csky/kernel/probes/kprobes.c | 5 -----
arch/csky/kernel/probes/uprobes.c | 6 ------
arch/riscv/kernel/probes/kprobes.c | 5 -----
arch/riscv/kernel/probes/uprobes.c | 6 ------
arch/s390/kernel/kprobes.c | 5 -----
arch/x86/kernel/kprobes/core.c | 5 -----
kernel/events/uprobes.c | 6 ++++++
kernel/kprobes.c | 5 +++++
10 files changed, 11 insertions(+), 44 deletions(-)
--
2.17.1
next reply other threads:[~2022-09-17 1:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 1:55 Yipeng Zou [this message]
2022-09-17 1:55 ` [PATCH 1/2] kprobes: make arch_init_kprobes as weak Yipeng Zou
2022-09-17 1:55 ` [PATCH 2/2] uprobes: make arch_uprobe_exception_notify " Yipeng Zou
2022-09-17 10:58 ` [PATCH 0/2] make weak attributes in {k,u}probes Guo Ren
2022-09-20 17:02 ` Naveen N. Rao
2022-09-21 8:25 ` Peter Zijlstra
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=20220917015522.44583-1-zouyipeng@huawei.com \
--to=zouyipeng@huawei.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=borntraeger@linux.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=chris.zjh@huawei.com \
--cc=dave.hansen@linux.intel.com \
--cc=gor@linux.ibm.com \
--cc=guoren@kernel.org \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=liaochang1@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=namit@vmware.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).