From: Wolfgang Mauerer <wolfgang.mauerer@siemens.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>,
"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] [RFC PATCH 0/10] Support ftrace on ipipe kernels
Date: Fri, 21 Dec 2012 17:47:00 +0100 [thread overview]
Message-ID: <50D49284.6070504@siemens.com> (raw)
In-Reply-To: <50D48EE0.5050407@xenomai.org>
On 21/12/12 17:31, Philippe Gerum wrote:
> On 12/21/2012 02:26 PM, Wolfgang Mauerer wrote:
>> Hi Gilles, Jan,
>>
>> here's a proposal to make ipipe compatible with ftrace that
>> does not require global modifications to the preemption system,
>> but makes do with local changes. The approach should be easy
>> to maintain in the long run:
>>
>
> In the long run, we won't have any non-linux stacks to deal with.
> Xenomai 3.x will be moving kernel-based threads over regular linux
> kthreads soon, the conversion has begun today in my local tree actually.
> I guess that nobody is going to be saddened to see this non-sense go
> away (yes, I'm the original author of this non-sense, it's painful enough).
>
> So basically, this patches series will be required for running the 2.6.x
> series only. For this reason, on a general note, I'd like to see all
> these extra bits moving to the legacy section in a way or another
> (CONFIG_IPIPE_LEGACY).
sure, that's easy enough to do.
Thanks, Wolfgang
prev parent reply other threads:[~2012-12-21 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 13:26 [Xenomai] [RFC PATCH 0/10] Support ftrace on ipipe kernels Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 01/10] ipipe: Add root domain guard to preempt_schedule Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 02/10] ipipe: Harden clocks used by ftrace and perf Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 03/10] ipipe: Harden ftrace function and function-graph tracer Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 04/10] Harden trace_vbprintk for non-root use Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 05/10] ipipe: Remove superfluous include file in ipipe.h Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 06/10] ipipe: safe thread_info access from non-root context Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 07/10] ipipe: Add mechanism to allow preemption calls " Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 08/10] ipipe: Introduce preemption call replacement mechanism Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 09/10] ipipe: Fix CONFIG_PREEMPT build Wolfgang Mauerer
2012-12-21 13:26 ` [Xenomai] [PATCH 10/10] ipipe: Make ftrace compatible with ipipe Wolfgang Mauerer
2012-12-21 16:31 ` [Xenomai] [RFC PATCH 0/10] Support ftrace on ipipe kernels Philippe Gerum
2012-12-21 16:47 ` Wolfgang Mauerer [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=50D49284.6070504@siemens.com \
--to=wolfgang.mauerer@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=rpm@xenomai.org \
--cc=xenomai@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.