From: Dario Faggioli <dario.faggioli@citrix.com>
To: Simon Martin <smartin@milliways.cl>
Cc: Lars Kurth <lars.kurth@citrix.com>,
Roland Heusser <heusserr@mail.gvsu.edu>,
Artem Mygaiev <artem.mygaiev@globallogic.com>,
Lovene Bhatia <lbhatia@samsung.com>, Sisu Xi <xisisu@gmail.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Joshua Whitehead <whitehej@mail.gvsu.edu>,
xen-devel <xen-devel@lists.xen.org>,
Drek Darkover <wackerei@gmail.com>,
Stefano Panella <stefano.panella@citrix.com>,
Nate Studer <nate.studer@dornerworks.com>,
mdavis@planetaryresources.com
Subject: Re: Xen for real-time/embedded/automotive
Date: Thu, 28 Nov 2013 10:53:21 +0100 [thread overview]
Message-ID: <1385632401.20797.55.camel@Abyss> (raw)
In-Reply-To: <em44f0aed9-fe78-4dae-bf48-10157d648060@smartin-alien>
[-- Attachment #1.1: Type: text/plain, Size: 2743 bytes --]
On mar, 2013-11-19 at 01:27 +0000, Simon Martin wrote:
> From my limited development here I would say the following:
>
> 1.- The embedded systems I work on have just a flat memory space, no
> MMU or anything like that, so the Mini-OS example is total overkill.
> I am writing a real minimalist PV guest based on that but it's amazing
> how time consuming it's being. I'll be returning this to the project
> when I'm happy with it, as long as you want it.
>
I totally see what you mean! I'm glad that you find, also thanks to this
thread, some nice similarities with MirageOS, and some chance for
possible collaborations that were even beyond the original purpose of
this very thread... That's why Open Source is so awesome, isn't it?
> 2.- As far as I am concerned there are 2 metrics that I will be
> analysing once I have my little PV guest running: latency and jitter.
> As far as I am concerned, jitter can be worst that latency. In some
> systems you can compensate for latency, however jitter is much more
> difficult to handle.
>
These indeed are very important aspects of a truly real-time enabling
platform. As I said in the e-mail starting this, I'm committed to start
monitoring these, to at least assess where we stand.
I'll keep this thread informed about that, of course.
For now, for the benefits of all the people in this thread, let me use
his mail to direct you to the code of the "minimalistic" PV guest port
that Simon is working on, and that he kindly published here:
"A Xen Micro Paravirtualized Guest to load a small independent OS"
https://github.com/FurryFuttock/micro-pv
Thanks a lot Simon for doing and releasing this, I'm _sure_ it'll be
helpful for others, and for the prosecution of this discussion/activity.
BTW, I do realise only know that I probably never asked that... What is
(if you feel like saying it here) your specific usecase / final goal of
this work?
> 3.- At the moment I am assuming that I will access a PCI NIC directly
> from the PV guest. Would be nice to have a deterministic network
> access via Dom0 drivers so I can carry on playing in virtual land.
> This can be generalised to other hardware too.
>
That's another interesting piece of work Sisu was also referring too
(saying that they're doing some research on it, which is always fine).
Like it usually happens, we don't risk to get in short of things to do
that soon, do we? :-P
Thanks and Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-28 9:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 19:14 Xen for real-time/embedded/automotive Dario Faggioli
2013-11-19 1:27 ` Simon Martin
2013-11-20 14:04 ` Lars Kurth
2013-11-20 14:23 ` Simon Martin
2013-11-20 15:14 ` Lars Kurth
2013-11-20 17:36 ` Anil Madhavapeddy
2013-11-20 17:59 ` Simon Martin
2013-11-20 18:05 ` Anil Madhavapeddy
2013-11-20 18:35 ` Simon Martin
2013-11-28 9:53 ` Dario Faggioli [this message]
2013-11-28 11:39 ` Simon Martin
2013-11-28 12:03 ` Dario Faggioli
2013-11-28 12:39 ` Simon Martin
2013-11-30 11:37 ` Dario Faggioli
2013-11-20 4:50 ` Sisu Xi
2013-11-20 15:25 ` Lars Kurth
2013-11-21 7:04 ` Dario Faggioli
2013-11-21 7:52 ` Dario Faggioli
2013-12-12 8:05 ` Jeremiah Foster
2013-12-12 8:12 ` Dario Faggioli
2013-12-12 9:35 ` Lars Kurth
2013-12-12 9:39 ` Jeremiah Foster
2013-12-12 9:46 ` Dario Faggioli
2013-11-22 7:14 ` Dario Faggioli
2013-11-28 9:35 ` Dario Faggioli
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=1385632401.20797.55.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=artem.mygaiev@globallogic.com \
--cc=heusserr@mail.gvsu.edu \
--cc=lars.kurth@citrix.com \
--cc=lbhatia@samsung.com \
--cc=mdavis@planetaryresources.com \
--cc=nate.studer@dornerworks.com \
--cc=smartin@milliways.cl \
--cc=stefano.panella@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wackerei@gmail.com \
--cc=whitehej@mail.gvsu.edu \
--cc=xen-devel@lists.xen.org \
--cc=xisisu@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).