mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Li Zefan <lizf@cn.fujitsu.com>
Subject: [GIT PULL] tracing/kprobes: kprobes fixes
Date: Sat,  3 Oct 2009 04:31:28 +0200	[thread overview]
Message-ID: <1254537091-4993-1-git-send-email-fweisbec@gmail.com> (raw)

Ingo,

Please pull the tracing/kprobes tree that can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	tracing/kprobes

(I'm just waiting a bit before pushing the perf probe patches
while we discuss some syntax things).

Thanks.

Masami Hiramatsu (3):
      tracing/kprobes: Use global event perf buffers in kprobe tracer
      x86: Add VIA processor instructions in opcodes decoder
      tracing/ftrace: Fix to check create_event_dir() when adding new events

 arch/x86/lib/x86-opcode-map.txt |    8 +++-
 kernel/trace/trace_events.c     |   25 +++++----
 kernel/trace/trace_kprobe.c     |  115 +++++++++++++++++++++++++--------------
 3 files changed, 94 insertions(+), 54 deletions(-)

             reply	other threads:[~2009-10-03  2:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03  2:31 Frederic Weisbecker [this message]
2009-10-03  2:31 ` [PATCH 1/3] tracing/kprobes: Use global event perf buffers in kprobe tracer Frederic Weisbecker
2009-10-03  2:31 ` [PATCH 2/3] x86: Add VIA processor instructions in opcodes decoder Frederic Weisbecker
2009-10-03  2:31 ` [PATCH 3/3] tracing/ftrace: Fix to check create_event_dir() when adding new events Frederic Weisbecker
2009-10-03 10:35 ` [GIT PULL] tracing/kprobes: kprobes fixes Ingo Molnar
2009-10-03 10:49   ` Ingo Molnar

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=1254537091-4993-1-git-send-email-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®