From: Jan Kiszka <jan.kiszka@domain.hid>
To: Alessio Igor Bogani <abogani@domain.hid>
Cc: "Xenomai (help)" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Xenomai & Xen
Date: Fri, 27 Oct 2006 15:17:31 +0200 [thread overview]
Message-ID: <454206EB.1050807@domain.hid> (raw)
In-Reply-To: <1161936364.5241.33.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
Alessio Igor Bogani wrote:
> Hi,
>
> [...]
>>> Can Xenomai cohabit with Xen in the same kernel?
>>> Someone have already tried?
>> As paravirtualised host of Xen or by driving Xen in real-time via
s/host/guest/, of course.
> Xenomai?
>
> The second one:
>
> HW -> Adeos-ipipe -> Xen-Domai0 ---> Xen unprivileged domain A
> |--> Xen unprivileged domain B
> |--> ....
> ---> Xen unprivileged domain N
>
> It is possible?
Well, nothing is impossible. But what do you want to achieve?
If we are now just talking about Adeos/I-pipe (which is a project of its
own), it will help you to dispatch hardware IRQs, faults, and specific
events generated inside the I-pipe root domain to multiple prioritised
users (i.e. "pipelined"). In your scenario above there is only one user
so far, Xen.
Or do you plan to attach Xenomai as an I-pipe domain and push it before
Xen? The point about Xenomai is then that it tightly cooperates with
Linux (even if you keep your applications only in kernel space). But
what Linux to use in a Xen-virtualised Environment? One of the
unprivileged Xen domains? That's something one has to consider
carefully, and I cannot give you a quick answer about potential traps
and pitfalls (there are always some...).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2006-10-27 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 14:51 [Xenomai-help] Xenomai & Xen Alessio Igor Bogani
2006-10-26 16:13 ` Jan Kiszka
2006-10-27 8:06 ` Alessio Igor Bogani
2006-10-27 13:17 ` 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=454206EB.1050807@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=abogani@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.