All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>
Subject: [Adeos-main] [pull request] Improve ftrace interaction
Date: Tue, 09 Mar 2010 19:04:37 +0100	[thread overview]
Message-ID: <4B968DB5.5020302@domain.hid> (raw)

The following changes since commit 7c90959b7e4eb5ef8a775ec17005c23f30daade1:
  Philippe Gerum (1):
        ipipe: introduce 3-level IRQ pending map

are available in the git repository at:

  git://git.kiszka.org/ipipe-2.6 queues/2.6.32-noarch

These patches address various possible configuration errors around
ftrace that can cause hard crashes over I-pipe kernels. Moreover, one
patch enables the safe use of ftrace's PID filtering that comes for free
for the I-pipe tracer now.

The patches also apply on 2.6.33-noarch but were only tested on
2.6.32-x86.


Jan Kiszka (5):
      Use ipipe_safe_current in ftrace_pid_func
      Prevent unsafe ftrace usage over I-pipe
      Disable branch tracing/profiling under I-pipe
      Do no kill ftrace on failing function test
      Fix ipipe_safe_current definition for !CONFIG_IPIPE

 include/linux/ftrace.h        |    1 +
 include/linux/ipipe.h         |    2 +-
 kernel/ipipe/tracer.c         |    3 ++-
 kernel/trace/Kconfig          |    2 ++
 kernel/trace/ftrace.c         |    7 ++++++-
 kernel/trace/trace_selftest.c |    2 ++
 6 files changed, 14 insertions(+), 3 deletions(-)


             reply	other threads:[~2010-03-09 18:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-09 18:04 Jan Kiszka [this message]
2010-03-13 15:59 ` [Adeos-main] [pull request] Improve ftrace interaction Philippe Gerum
2010-03-14  9:00   ` Jan Kiszka

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=4B968DB5.5020302@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=adeos-main@gna.org \
    --cc=rpm@xenomai.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.