All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jean Rodriguez <j.rodriguez@caustier.com>, xenomai@xenomai.org
Subject: Re: [Xenomai] Some Information About compilation Xenomai and RT Patches
Date: Fri, 20 Jun 2014 11:00:29 +0200	[thread overview]
Message-ID: <53A3F82D.5090401@xenomai.org> (raw)
In-Reply-To: <006d01cf8a3c$dee76050$9cb620f0$@caustier.com>

On 06/17/2014 05:00 PM, Jean Rodriguez wrote:
> Hi guys,
>
> I’m trying to compile kernel 3.8 with the last xenomai source.
>
> I want to know some precisions about preempt option.
>
> Is it useless to patch the kernel with with Xenomai and also with RT patch
> from kernel.org?

Combining both makes sense only if your use case involves response time 
requirements when running regular linux activities, in addition to the 
real-time duties offloaded to the Xenomai co-kernel. In most cases where 
a dual kernel solution applies, there is no requirement for full 
preemption (-rt) on the regular linux side though.

>
> Because With RT patch I can choose on menuconfig  Preemption Model 5 choices
> (No preempt, Voluntary and low latency , preemptible kernel or fully
> preemptivekernel)
>
> But if I patch only with xenomai I have just 3 choices of preemptive (No
> preempt, Voluntary and low latency)
>

Those choices affect the regular linux kernel behavior only, not 
Xenomai. When the Xenomai co-kernel is present, there is no need for 
additional preemption models, the linux kernel is inherently preemptible 
by Xenomai activities at any time.

> If patch first with RT and after xenomai I have a lot of Hunk message
> (warning and error) but if  I Patch first with xenomai and after RT -> no
> problem
>
>
>
> So my question are they compatible together? Or perhaps choosing fully
> preemptive will turn my system unstable.
>

Combining both is possible, and such configuration is actually used by 
some projects. However, a combo patch merging preempt-rt and the I-pipe 
has to be specifically crafted for the target kernel.

>
>
> My goal is to catch Interruption with a small latency (50-10 µs) with a low
> processor charge

Since there is no one-fits-it-all solution, I would suggest to benchmark 
each configuration separately for your use case, and see which one best 
fits the bill, taking into account the pros and cons of each approach in 
the long run for your project.

>
> Board  Arbor card
> <http://www.arbor.com.tw/product/product.aspx?Product_Name=EmETX-i2900&os_id
> =1&version=+Default> EmETX-i2900  with ATOM N450
>
>
>
>
>
> Thanks for your future response
>
>
>
>
>
> Kind regards,
>
>
>
> Jean Rodriguez
>
> Ingénieur R&D Informatique
>
>
>
>
>
>
>
>
>
>
>
>
>
> ---
> Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection avast! Antivirus est active.
> http://www.avast.com
> _______________________________________________
> Xenomai mailing list
> Xenomai@xenomai.org
> http://www.xenomai.org/mailman/listinfo/xenomai
>


-- 
Philippe.


  parent reply	other threads:[~2014-06-20  9:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-17 15:00 [Xenomai] Some Information About compilation Xenomai and RT Patches Jean Rodriguez
     [not found] ` <be428e33f9f5482aa36cbc1654ec2db2@EX132MBOX1B.de2.local>
2014-06-20  8:50   ` Stoidner, Christoph
2014-06-20  9:00 ` Philippe Gerum [this message]
2014-06-20  9:02 ` Stoidner, Christoph
2014-06-20 11:50   ` Gilles Chanteperdrix
2014-06-23  9:33     ` Stoidner, Christoph
2014-06-23  9:40       ` Gilles Chanteperdrix
2014-06-23  9:53       ` Gilles Chanteperdrix
2014-06-23 10:04         ` Stoidner, Christoph
2014-06-23 23:41           ` Gilles Chanteperdrix
2014-06-24  6:37             ` Gilles Chanteperdrix

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=53A3F82D.5090401@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=j.rodriguez@caustier.com \
    --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.