LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org> To: Steven Rostedt <rostedt@goodmis.org> Cc: Ingo Molnar <mingo@kernel.org>, "Naveen N . Rao" <naveen.n.rao@linux.ibm.com>, Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>, "David S . Miller" <davem@davemloft.net>, Masami Hiramatsu <mhiramat@kernel.org>, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: [PATCH v2 1/2] kprobes: Initialize kprobes at postcore_initcall Date: Wed, 22 May 2019 17:32:27 +0900 [thread overview] Message-ID: <155851394736.15728.13626739508905120098.stgit@devnote2> (raw) In-Reply-To: <155851393823.15728.9489409117921369593.stgit@devnote2> Initialize kprobes at postcore_initcall level instead of module_init since kprobes is not a module, and it depends on only subsystems initialized in core_initcall. This will allow ftrace kprobe event to add new events when it is initializing because ftrace kprobe event is initialized at later initcall level. Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org> --- Changes in v2 - use postcore_initcall instead of subsys_initcall --- kernel/kprobes.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/kernel/kprobes.c b/kernel/kprobes.c index c83e54727131..5d51dd84b1a2 100644 --- a/kernel/kprobes.c +++ b/kernel/kprobes.c @@ -2291,6 +2291,7 @@ static int __init init_kprobes(void) init_test_probes(); return err; } +postcore_initcall(init_kprobes); #ifdef CONFIG_DEBUG_FS static void report_probe(struct seq_file *pi, struct kprobe *p, @@ -2616,5 +2617,3 @@ static int __init debugfs_kprobe_init(void) late_initcall(debugfs_kprobe_init); #endif /* CONFIG_DEBUG_FS */ - -module_init(init_kprobes);
next prev parent reply other threads:[~2019-05-22 8:32 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-22 8:32 [PATCH v2 0/2] Enable new kprobe event at boot Masami Hiramatsu 2019-05-22 8:32 ` Masami Hiramatsu [this message] 2019-05-22 8:32 ` [PATCH v2 2/2] tracing/kprobe: Add kprobe_event= boot parameter Masami Hiramatsu 2019-05-28 12:23 ` Anders Roxell 2019-05-28 12:36 ` Steven Rostedt 2019-05-28 13:39 ` Anders Roxell 2019-06-03 11:52 ` Masami Hiramatsu 2019-06-03 12:41 ` Masami Hiramatsu 2019-06-03 13:04 ` [PATCH] kprobes: Fix to init kprobes in subsys_initcall Masami Hiramatsu 2019-06-03 20:33 ` Anders Roxell 2019-06-04 9:06 ` Steven Rostedt 2019-06-04 15:56 ` Masami Hiramatsu 2019-06-12 7:59 ` Masami Hiramatsu 2019-06-12 13:47 ` Steven Rostedt 2019-06-13 7:08 ` Masami Hiramatsu 2019-06-14 20:38 ` Steven Rostedt
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=155851394736.15728.13626739508905120098.stgit@devnote2 \ --to=mhiramat@kernel.org \ --cc=anil.s.keshavamurthy@intel.com \ --cc=davem@davemloft.net \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=naveen.n.rao@linux.ibm.com \ --cc=rostedt@goodmis.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: linkBe 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).