From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: adeos-main <adeos-main@gna.org>
Subject: Re: [Adeos-main] [pull request] Improve ftrace interaction
Date: Sun, 14 Mar 2010 10:00:00 +0100 [thread overview]
Message-ID: <4B9CA590.7040102@domain.hid> (raw)
In-Reply-To: <1268495969.27899.144.camel@domain.hid>
[-- Attachment #1.1: Type: text/plain, Size: 1267 bytes --]
Philippe Gerum wrote:
> On Tue, 2010-03-09 at 19:04 +0100, Jan Kiszka wrote:
>> 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
>
> This one looks pretty ugly. I would rather define a entry point for
> registering ftrace hooks allowed to run in NMI context, and deny the
> regular unsafe registration routine when the I-pipe tracer is enabled.
I just learned yesterday from Frederic that the ftrace ring buffer
should be NMI-safe by now. I need to look into this again, maybe we can
make _much_ more of ftrace usable for I-pipe. IOW: Series on hold.
Jan
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 258 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2010-03-14 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 18:04 [Adeos-main] [pull request] Improve ftrace interaction Jan Kiszka
2010-03-13 15:59 ` Philippe Gerum
2010-03-14 9:00 ` Jan Kiszka [this message]
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=4B9CA590.7040102@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.