linux-perf-users.vger.kernel.org archive mirror
 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 <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] perf fixes
Date: Sat, 6 Aug 2022 21:10:36 +0200	[thread overview]
Message-ID: <Yu68rPjbQXEJlrdj@gmail.com> (raw)

Linus,

Please pull the latest perf/urgent git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-2022-08-06

   # HEAD: 99643bab36b642be10bf09cd3285c37c9e5b597f perf/core: Fix ';;' typo

Misc fixes to kprobes and the faddr2line script, plus a cleanup.

 Thanks,

	Ingo

------------------>
Chen Zhongjin (1):
      kprobes: Forbid probing on trampoline and BPF code areas

Josh Poimboeuf (2):
      scripts/faddr2line: Fix vmlinux detection on arm64
      scripts/faddr2line: Add CONFIG_DEBUG_INFO check

Masami Hiramatsu (Google) (1):
      x86/kprobes: Update kcb status flag after singlestepping

Slark Xiao (1):
      perf/core: Fix ';;' typo


 arch/x86/kernel/kprobes/core.c | 18 +++++++++++-------
 kernel/events/core.c           |  2 +-
 kernel/kprobes.c               |  3 ++-
 scripts/faddr2line             |  7 ++++++-
 4 files changed, 20 insertions(+), 10 deletions(-)

             reply	other threads:[~2022-08-06 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-06 19:10 Ingo Molnar [this message]
2022-08-07  0:50 ` [GIT PULL] perf fixes pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2022-08-28 14:35 Ingo Molnar
2022-08-28 18:18 ` 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=Yu68rPjbQXEJlrdj@gmail.com \
    --to=mingo@kernel.org \
    --cc=acme@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 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).