All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: ROSSIER Daniel <Daniel.Rossier@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Running Xenomai in a virtual machine
Date: Mon, 22 Jun 2009 15:55:03 +0200	[thread overview]
Message-ID: <4A3F8D37.2040908@domain.hid> (raw)
In-Reply-To: <D39BC4B7B612C6428144D37C54379A2F01A24CC99631@domain.hid>

ROSSIER Daniel wrote:
> Just going through this interesting thread, I though it might be of interest - probably not fully related to the topic, but... - to know
> that we are currently working on some integration efforts of Xenomai on top of the XEN hypervisor in the context of the
> embeddedXEN project. For the time being, it is purely devoted to ARM-based processors.
> 
> In case of interest, please visit: https://sourceforge.net/projects/embeddedxen. Xenomai will appear as a natural subtree of embeddedXEN, like xen or minios,
> but currently it is not present yet. The hypervisor and miniOS boots up in Mainstone/QEMU and soon on a Colibri/PXA270 board. EmbeddedXEN is mainly devoted to integrate multiple kernels into a single binary image for embedded systems with the support of hard realtime (domainU-RT, a new kind of Xen domain).

Interesting, will have a look (again). Last time I checked was two years
ago when MontaVista (IIRC) announced it. Does/will this version Xen not
suffer from the RT problems Xen upstream has, e.g. lacking preemptibility?

And what will be the impact on Xenomai? A new sub-arch per real arch?
Will Xenomai run stand-alone or together with a Linux kernel as on real
silicon? In the former case, what will be the programming model,
specifically regarding RT<->non-RT communication?

Jan

-- 
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux


  reply	other threads:[~2009-06-22 13:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  9:40 [Xenomai-help] Running Xenomai in a virtual machine Peter Soetens
2009-06-12  9:48 ` Sebastian Smolorz
2009-06-12 11:02   ` Jan Kiszka
2009-06-12 11:14     ` Peter Soetens
2009-06-12 12:42     ` Johan Visser
2009-06-12 13:00       ` Jan Kiszka
2009-06-12 13:10         ` Jan Kiszka
2009-06-12 14:33           ` Johan Visser
2009-06-22 13:15             ` ROSSIER Daniel
2009-06-22 13:55               ` Jan Kiszka [this message]
2009-06-22 14:05                 ` ROSSIER Daniel
2009-06-22 14:26                   ` Gilles Chanteperdrix
2009-06-22 15:05                     ` ROSSIER Daniel
2009-06-22 15:17                       ` Gilles Chanteperdrix
2009-06-22 15:45                         ` ROSSIER Daniel
2009-06-12 13:16         ` Gilles Chanteperdrix
2009-06-12 13:25           ` Jan Kiszka
2009-06-22 20:46             ` Johan Visser

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=4A3F8D37.2040908@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Daniel.Rossier@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.