From: Philippe Gerum <rpm@xenomai.org>
To: Leopold Palomo-Avellaneda <leo@alaxarxa.net>,
Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Packaging Xenomai-3
Date: Sun, 25 Jan 2015 10:14:57 +0100 [thread overview]
Message-ID: <54C4B411.3030307@xenomai.org> (raw)
In-Reply-To: <201501241756.28192.leo@alaxarxa.net>
On 01/24/2015 06:56 PM, Leopold Palomo-Avellaneda wrote:
> A Divendres, 23 de gener de 2015, Gilles Chanteperdrix va escriure:
>> On Fri, Jan 23, 2015 at 05:50:07PM +0100, Leopold Palomo-Avellaneda wrote:
>>> El Divendres, 23 de gener de 2015, a les 16:52:31, Gilles Chanteperdrix
>>> va
>>>
>>> escriure:
>>>> On Fri, Jan 23, 2015 at 01:09:41PM +0100, Leopold Palomo-Avellaneda
> wrote:
>>>>> Hi,
>>>>>
>>>>> now that I have some kernel to boot, I would like to ask some aspects
>>>>> of Xenomai-3 in order to package it.
>>>>>
>>>>> Reading the documentation, now the new libxenomai could use two kind
>>>>> of kernels: the patched one (Cobalt) or the preempt_rt (Mercury).
>>>>
>>>> a preempt_rt kernel is a patched kernel too.
>>>
>>> Writing the email I thought, both are patches, but I thought preempt_rt
>>> was integrated in mainline.
>>
>> No it is not.
>>
>>>>> 1) Is it possible to have _only_ one library (binary) that uses one
>>>>> or another kernel in function which is running?
>>>>
>>>> No, you could want to run a kernel with both patches. So basing the
>>>> decision on which patch you are running does not make sense.
>>>
>>> I don't want to run a kernel with both patches. It has no sense. But I
>>> could have binary packages that could work with both kernels. That was
>>> my idea.
>>
>> To the contrary, it has a lot of sense. You get one grade of
>> real-time for cobalt task, and another grade of real-time for tasks
>> scheduled by Linux.
>
> Maybe ... it could be interesting as an experiment.
No, it's not just an experiment. I'm aware of production setups which
have been running this configuration since 2009. I did the mixed
ipipe+prempt-rt port for them.
>
> Just for curiosity, have you had the test comparing in mercury and cobalt in
> the same harware with the same problem?
>
Yes, without any issue. Just use two different install roots, one for
cobalt, the other for mercury.
--
Philippe.
next prev parent reply other threads:[~2015-01-25 9:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 12:09 [Xenomai] Packaging Xenomai-3 Leopold Palomo-Avellaneda
2015-01-23 15:52 ` Gilles Chanteperdrix
2015-01-23 16:50 ` Leopold Palomo-Avellaneda
2015-01-23 17:27 ` Gilles Chanteperdrix
2015-01-24 17:56 ` Leopold Palomo-Avellaneda
2015-01-25 9:14 ` Philippe Gerum [this message]
2015-01-25 11:14 ` Leopold Palomo-Avellaneda
2015-01-25 18:10 ` Philippe Gerum
2015-01-25 18:43 ` Leopold Palomo-Avellaneda
2015-01-26 12:08 ` Gilles Chanteperdrix
2015-01-26 12:39 ` Leopold Palomo-Avellaneda
2015-01-26 13:38 ` Daniele Nicolodi
2015-01-26 14:17 ` Leopold Palomo-Avellaneda
2015-01-26 14:24 ` Daniele Nicolodi
2015-01-26 14:01 ` Philippe Gerum
2015-01-26 14:47 ` Leopold Palomo-Avellaneda
2015-01-26 14:55 ` Gilles Chanteperdrix
2015-01-26 14:08 ` Gilles Chanteperdrix
2015-01-26 14:56 ` Leopold Palomo-Avellaneda
2015-01-26 14:59 ` Gilles Chanteperdrix
2015-01-26 17:46 ` Leopold Palomo-Avellaneda
2015-01-26 18:20 ` Gilles Chanteperdrix
2015-01-26 22:17 ` Leopold Palomo-Avellaneda
2015-01-26 22:26 ` Daniele Nicolodi
2015-01-26 22:57 ` Leopold Palomo-Avellaneda
2015-01-26 18:32 ` Gilles Chanteperdrix
2015-01-26 22:19 ` Leopold Palomo-Avellaneda
2015-01-23 16:04 ` Philippe Gerum
2015-01-23 17:02 ` Leopold Palomo-Avellaneda
2015-01-23 17:24 ` Philippe Gerum
2015-01-23 17:47 ` Gilles Chanteperdrix
2015-01-24 10:05 ` Philippe Gerum
2015-01-24 17:43 ` Leopold Palomo-Avellaneda
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=54C4B411.3030307@xenomai.org \
--to=rpm@xenomai.org \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=leo@alaxarxa.net \
--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.