All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] perf/kprobes changes for v5.10
Date: Mon, 12 Oct 2020 18:23:37 +0200	[thread overview]
Message-ID: <20201012162337.GA3751519@gmail.com> (raw)

Linus,

Please pull the latest perf/kprobes git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-kprobes-2020-10-12

   # HEAD: bcb53209be5cb32d485507452edda19b78f31d84 kprobes: Fix to check probe enabled before disarm_kprobe_ftrace()

This tree prepares to unify the kretprobe trampoline handler and make
kretprobe lockless. (Those patches are still work in progress.)

 Thanks,

	Ingo

------------------>
Masami Hiramatsu (17):
      kprobes: Add generic kretprobe trampoline handler
      x86/kprobes: Use generic kretprobe trampoline handler
      arm: kprobes: Use generic kretprobe trampoline handler
      arm64: kprobes: Use generic kretprobe trampoline handler
      arc: kprobes: Use generic kretprobe trampoline handler
      csky: kprobes: Use generic kretprobe trampoline handler
      ia64: kprobes: Use generic kretprobe trampoline handler
      mips: kprobes: Use generic kretprobe trampoline handler
      parisc: kprobes: Use generic kretprobe trampoline handler
      powerpc: kprobes: Use generic kretprobe trampoline handler
      s390: kprobes: Use generic kretprobe trampoline handler
      sh: kprobes: Use generic kretprobe trampoline handler
      sparc: kprobes: Use generic kretprobe trampoline handler
      kprobes: Remove NMI context check
      kprobes: Free kretprobe_instance with RCU callback
      kprobes: Make local functions static
      kprobes: Fix to check probe enabled before disarm_kprobe_ftrace()


 arch/arc/kernel/kprobes.c          |  54 +--------------
 arch/arm/probes/kprobes/core.c     |  78 +---------------------
 arch/arm64/kernel/probes/kprobes.c |  78 +---------------------
 arch/csky/kernel/probes/kprobes.c  |  77 +--------------------
 arch/ia64/kernel/kprobes.c         |  77 +--------------------
 arch/mips/kernel/kprobes.c         |  54 +--------------
 arch/parisc/kernel/kprobes.c       |  76 ++-------------------
 arch/powerpc/kernel/kprobes.c      |  53 +--------------
 arch/s390/kernel/kprobes.c         |  79 +---------------------
 arch/sh/kernel/kprobes.c           |  58 +---------------
 arch/sparc/kernel/kprobes.c        |  51 +-------------
 arch/x86/kernel/kprobes/core.c     | 108 +-----------------------------
 include/linux/kprobes.h            |  51 ++++++++------
 kernel/kprobes.c                   | 133 +++++++++++++++++++++++++++++--------
 14 files changed, 169 insertions(+), 858 deletions(-)

             reply	other threads:[~2020-10-12 16:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-12 16:23 Ingo Molnar [this message]
2020-10-12 21:25 ` [GIT PULL] perf/kprobes changes for v5.10 pr-tracker-bot

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=20201012162337.GA3751519@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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.