From: Li Huafei <lihuafei1@huawei.com>
To: <mark.rutland@arm.com>, <catalin.marinas@arm.com>, <will@kernel.org>
Cc: <rostedt@goodmis.org>, <mingo@redhat.com>,
<Julia.Lawall@inria.fr>, <akpm@linux-foundation.org>,
<andreyknvl@gmail.com>, <elver@google.com>,
<wangkefeng.wang@huawei.com>, <zhouchengming@bytedance.com>,
<ardb@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <lihuafei1@huawei.com>
Subject: [PATCH 0/3] arm64: module/ftrace: Fix mcount-based ftrace initialization failure
Date: Thu, 29 Sep 2022 17:41:31 +0800 [thread overview]
Message-ID: <20220929094134.99512-1-lihuafei1@huawei.com> (raw)
This series is mainly to fix the mcount-based ftrace initialization
failure during module loading (see patch 3). The first two are cleanup
patches.
Li Huafei (3):
arm64: module: Make plt_equals_entry() static
arm64: module: Remove unused plt_entry_is_initialized()
arm64: module/ftrace: Fix mcount-based ftrace initialization failure
arch/arm64/include/asm/module.h | 13 +++++++------
arch/arm64/kernel/ftrace.c | 29 ++++++++++++++++++++++++++++-
arch/arm64/kernel/module-plts.c | 19 ++++++++++++++++++-
arch/arm64/kernel/module.c | 11 +++++++++++
4 files changed, 64 insertions(+), 8 deletions(-)
base-commit: c3e0e1e23c70455916ff3472072437b3605c6cfe
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Li Huafei <lihuafei1@huawei.com>
To: <mark.rutland@arm.com>, <catalin.marinas@arm.com>, <will@kernel.org>
Cc: <rostedt@goodmis.org>, <mingo@redhat.com>,
<Julia.Lawall@inria.fr>, <akpm@linux-foundation.org>,
<andreyknvl@gmail.com>, <elver@google.com>,
<wangkefeng.wang@huawei.com>, <zhouchengming@bytedance.com>,
<ardb@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <lihuafei1@huawei.com>
Subject: [PATCH 0/3] arm64: module/ftrace: Fix mcount-based ftrace initialization failure
Date: Thu, 29 Sep 2022 17:41:31 +0800 [thread overview]
Message-ID: <20220929094134.99512-1-lihuafei1@huawei.com> (raw)
This series is mainly to fix the mcount-based ftrace initialization
failure during module loading (see patch 3). The first two are cleanup
patches.
Li Huafei (3):
arm64: module: Make plt_equals_entry() static
arm64: module: Remove unused plt_entry_is_initialized()
arm64: module/ftrace: Fix mcount-based ftrace initialization failure
arch/arm64/include/asm/module.h | 13 +++++++------
arch/arm64/kernel/ftrace.c | 29 ++++++++++++++++++++++++++++-
arch/arm64/kernel/module-plts.c | 19 ++++++++++++++++++-
arch/arm64/kernel/module.c | 11 +++++++++++
4 files changed, 64 insertions(+), 8 deletions(-)
base-commit: c3e0e1e23c70455916ff3472072437b3605c6cfe
--
2.17.1
next reply other threads:[~2022-09-29 9:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 9:41 Li Huafei [this message]
2022-09-29 9:41 ` [PATCH 0/3] arm64: module/ftrace: Fix mcount-based ftrace initialization failure Li Huafei
2022-09-29 9:41 ` [PATCH 1/3] arm64: module: Make plt_equals_entry() static Li Huafei
2022-09-29 9:41 ` Li Huafei
2022-09-29 11:27 ` Mark Rutland
2022-09-29 11:27 ` Mark Rutland
2022-09-29 9:41 ` [PATCH 2/3] arm64: module: Remove unused plt_entry_is_initialized() Li Huafei
2022-09-29 9:41 ` Li Huafei
2022-09-29 11:28 ` Mark Rutland
2022-09-29 11:28 ` Mark Rutland
2022-09-29 9:41 ` [PATCH 3/3] arm64: module/ftrace: Fix mcount-based ftrace initialization failure Li Huafei
2022-09-29 9:41 ` Li Huafei
2022-09-29 11:26 ` Mark Rutland
2022-09-29 11:26 ` Mark Rutland
2022-09-29 11:59 ` Mark Rutland
2022-09-29 11:59 ` Mark Rutland
2022-09-29 12:26 ` Li Huafei
2022-09-29 12:26 ` Li Huafei
2022-09-29 13:41 ` Mark Rutland
2022-09-29 13:41 ` Mark Rutland
2022-09-29 17:54 ` (subset) [PATCH 0/3] " Catalin Marinas
2022-09-29 17:54 ` Catalin Marinas
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=20220929094134.99512-1-lihuafei1@huawei.com \
--to=lihuafei1@huawei.com \
--cc=Julia.Lawall@inria.fr \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=elver@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=wangkefeng.wang@huawei.com \
--cc=will@kernel.org \
--cc=zhouchengming@bytedance.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.