All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Jonathan Daugherty <jtd@galois.com>
Cc: xen-users@lists.xen.org, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Xen-users] ANN: FreeRTOS 7.6.0 for Xen on ARM released
Date: Tue, 20 Jan 2015 10:14:11 +0000	[thread overview]
Message-ID: <1421748851.10440.194.camel@citrix.com> (raw)
In-Reply-To: <1421747758.10440.184.camel@citrix.com>

I failed on the CC, whoops! Lets try that again...

(see also some comments below)

On Tue, 2015-01-20 at 09:55 +0000, Ian Campbell wrote:
> Hi Jonathan,
> 
> Very cool!
> 
> I've copied xen-devel, since I bet there are folks there who would be
> interested too.
> 
> Ian.
> 
> On Mon, 2015-01-19 at 11:12 -0800, Jonathan Daugherty wrote:
> > Hi,
> > 
> > I'm pleased to announce that my port of FreeRTOS 7.6.0 for Xen on ARM is
> > now released!  Now you can deploy FreeRTOS alongside all of those tiny
> > Mirage VMs you have been running.  The source is available on GitHub:
> > 
> >   https://github.com/GaloisInc/FreeRTOS-Xen
> > 
> > I presented this work at last year's Xen Developer Summit, and it is
> > finally out. I am happy to accept community patches, address issues,
> > etc. To test your patches, you'll need an ARM system running Xen.
> > 
> > Many thanks to the Xen developers who helped us along the way!

BTW, I notice that you have hardcoded the GIC addresses and various
interrupt sources. We do not make any guarantees about the guest virtual
platform memory or interrupt layout beyond committing to correctly
describing them in the Device Tree Blob which is passed to the guest
kernel at start of day.

So anything built with this version of Free-RTOS will only work on Xen
4.4, which is something which should be made clear to users etc. In
particular please could you clarify the statement "Xen version: 4.4+" in
your README, since right now I think you only support 4.4.

Anyway, this is a valid design choice for you to make, so long as you
understand the constaints and consequences. If you want to make binaries
which are portable and/or to avoid having to have configuration nobs at
build time then the correct thing to do is to parse the DTB. The ARM
port of mini-os (xen.git/extras/mini-os) has some initial code to do
that, with other bits being in Thomas Leonard's remaining patches (I'm
not sure if even that is complete, but it is in the right direction).

Note that Xen 4.5 has moved a bunch of stuff around, in particular the
GIC, to make room for more guest low RAM.

Ian.

       reply	other threads:[~2015-01-20 10:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150119191238.GA15495@galois.com>
     [not found] ` <1421747758.10440.184.camel@citrix.com>
2015-01-20 10:14   ` Ian Campbell [this message]
2015-01-20 19:31     ` [Xen-users] ANN: FreeRTOS 7.6.0 for Xen on ARM released Jonathan Daugherty

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=1421748851.10440.194.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=jtd@galois.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xen-users@lists.xen.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.