From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andi Kleen <ak@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Jessica Yu <jeyu@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>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v5 1/6] kprobes: Remove dependency to the module_mutex
Date: Sat, 25 Jul 2020 05:48:34 +0300 [thread overview]
Message-ID: <20200725024834.GE17052@linux.intel.com> (raw)
In-Reply-To: <20200724234631.40f4ffec6adae57ac3df8ea3@kernel.org>
On Fri, Jul 24, 2020 at 11:46:31PM +0900, Masami Hiramatsu wrote:
> On Fri, 24 Jul 2020 08:05:48 +0300
> Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com> wrote:
>
> > Add lock_modules() and unlock_modules() wrappers for acquiring module_mutex
> > in order to remove the compile time dependency to it.
>
> This subject is a bit confusing. This is just wrapping modules_mutex in
> kpprobes. We still have compile time dependency, e.g. module_state, right?
Yes. This more like a preliminary change to make that happen. The
actual flagging is in 6/6 ("Remove CONFIG_MODULE dependency").
Maybe a better angle would be to make this update all sites that
deal with module_mutex [*] and base the whole rationale on that?
[*] https://lore.kernel.org/lkml/20200725024227.GD17052@linux.intel.com/
/Jarkko
next prev parent reply other threads:[~2020-07-25 2:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 5:05 [PATCH v5 0/6] arch/x86: kprobes: Remove MODULES dependency Jarkko Sakkinen
2020-07-24 5:05 ` [PATCH v5 1/6] kprobes: Remove dependency to the module_mutex Jarkko Sakkinen
2020-07-24 9:13 ` Ingo Molnar
2020-07-25 2:36 ` Jarkko Sakkinen
2020-07-24 9:17 ` Ingo Molnar
2020-07-25 3:01 ` Jarkko Sakkinen
2020-07-25 10:21 ` Ingo Molnar
2020-07-28 7:34 ` Masami Hiramatsu
2020-07-28 12:29 ` [tip: perf/core] kprobes: Remove unnecessary module_mutex locking from kprobe_optimizer() tip-bot2 for Masami Hiramatsu
2020-08-17 21:22 ` [PATCH v5 1/6] kprobes: Remove dependency to the module_mutex Jarkko Sakkinen
2020-07-24 10:22 ` Mike Rapoport
2020-07-25 2:42 ` Jarkko Sakkinen
2020-07-24 14:46 ` Masami Hiramatsu
2020-07-25 2:48 ` Jarkko Sakkinen [this message]
2020-07-24 5:05 ` [PATCH v5 2/6] vmalloc: Add text_alloc() and text_free() Jarkko Sakkinen
2020-07-24 10:22 ` Mike Rapoport
2020-07-25 2:20 ` Jarkko Sakkinen
2020-07-24 5:05 ` [PATCH v5 3/6] arch/x86: Implement " Jarkko Sakkinen
2020-07-24 9:22 ` Ingo Molnar
2020-07-25 2:03 ` Jarkko Sakkinen
2020-07-24 5:05 ` [PATCH v5 4/6] arch/x86: kprobes: Use " Jarkko Sakkinen
2020-07-24 5:05 ` [PATCH v5 5/6] " Jarkko Sakkinen
2020-07-24 9:27 ` Ingo Molnar
2020-07-24 12:16 ` Ard Biesheuvel
2020-07-25 3:19 ` [PATCH v5 5/6] kprobes: Use text_alloc() and text_free()] Jarkko Sakkinen
2020-07-25 3:16 ` [PATCH v5 5/6] kprobes: Use text_alloc() and text_free() Jarkko Sakkinen
2020-07-26 8:14 ` Mike Rapoport
2020-07-26 16:06 ` Ard Biesheuvel
2020-07-28 8:17 ` Masami Hiramatsu
2020-07-28 10:56 ` Ard Biesheuvel
2020-07-28 13:35 ` Masami Hiramatsu
2020-07-28 17:51 ` Ard Biesheuvel
2020-07-29 1:50 ` Masami Hiramatsu
2020-07-29 6:13 ` Ard Biesheuvel
2020-07-30 1:09 ` Masami Hiramatsu
2020-08-18 5:30 ` Jarkko Sakkinen
2020-08-18 11:51 ` Mike Rapoport
2020-08-18 16:30 ` Jarkko Sakkinen
2020-08-19 6:47 ` Mike Rapoport
2020-08-19 21:07 ` Jarkko Sakkinen
2020-07-24 10:27 ` Mike Rapoport
2020-07-24 14:57 ` Masami Hiramatsu
2020-07-24 23:38 ` Jarkko Sakkinen
2020-07-24 5:05 ` [PATCH v5 6/6] kprobes: Remove CONFIG_MODULES dependency Jarkko Sakkinen
2020-07-24 7:01 ` [PATCH v5 0/6] arch/x86: kprobes: Remove MODULES dependency Jarkko Sakkinen
2020-07-24 10:26 ` Mike Rapoport
-- strict thread matches above, loose matches on Subject: below --
2020-07-24 5:04 Jarkko Sakkinen
2020-07-24 5:04 ` [PATCH v5 1/6] kprobes: Remove dependency to the module_mutex Jarkko Sakkinen
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=20200725024834.GE17052@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=jeyu@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=naveen.n.rao@linux.ibm.com \
--cc=peterz@infradead.org \
--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: 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.