From: Philippe Gerum <rpm@xenomai.org>
To: Anisha Kaul <born.rebel.83@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Is it compulsory to apply the PREEMPT_RT patch (to Linux) when running Xenomai on the top of it?
Date: Tue, 03 Apr 2012 09:42:32 +0200 [thread overview]
Message-ID: <4F7AA9E8.5020900@domain.hid> (raw)
In-Reply-To: <CAM1yFZ_GGO0T7uwCx3_yNZMrc2b9pyt=6jgE5toyucmCrk0+JA@mail.gmail.com>
On 04/03/2012 09:37 AM, Anisha Kaul wrote:
> On 3 April 2012 12:48, Philippe Gerum<rpm@xenomai.org> wrote:
>>> No.
>>
>> I mean: this is not implied, and you don't need _RT (actually, to have it,
>> you would need a specific interrupt pipeline patch).
>
> Thanks for replying.
>
> I read that this patch allows nearly all of the kernel to be
> preempted, with the exception of a few very small regions of code
> ("raw_spinlock critical regions"), can you please point out a few
> cases in which actually we "should" apply this patch?
>
> Xenomai already gives a hard real time, so why would we need this
> patch? Any hints please?
>
>
This is a different approach to a same problem:
- _RT attempts to make the whole regular kernel real-time aware.
- Xenomai 2.x provides a co-kernel for exclusively handling real-time
processing.
There are pros and cons in the two approaches, this is basically why
Xenomai 3 will allow both.
> -Anisha
>
--
Philippe.
next prev parent reply other threads:[~2012-04-03 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 6:56 [Xenomai-help] Is it compulsory to apply the PREEMPT_RT patch (to Linux) when running Xenomai on the top of it? Anisha Kaul
2012-04-03 7:17 ` Philippe Gerum
2012-04-03 7:18 ` Philippe Gerum
2012-04-03 7:37 ` Anisha Kaul
2012-04-03 7:42 ` Philippe Gerum [this message]
2012-04-03 8:48 ` Anisha Kaul
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=4F7AA9E8.5020900@domain.hid \
--to=rpm@xenomai.org \
--cc=born.rebel.83@domain.hid \
--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.