xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Nate Studer <nate.studer@dornerworks.com>
To: Simon Martin <smartin@milliways.cl>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	Robert VanVossen <Robert.VanVossen@dornerworks.com>
Subject: Re: Mapping shared pages from Windows
Date: Wed, 30 Oct 2013 14:39:28 -0400	[thread overview]
Message-ID: <52715260.5@dornerworks.com> (raw)
In-Reply-To: <em3f302c90-e0ce-465f-8326-607b5eba69e9@smartin-alien>

On 10/27/2013 6:43 PM, Simon Martin wrote:
> I am porting a real-time embedded OS that I originally developed on a Texas
> Instruments TMS320C3x DSP on proprietary hardware. This was then ported to
> MIPS64 (again on proprietary hardware) and now finally it's running on an ARM9.
> I have already ported this to a Windows user space application and run it as a
> simulator. Of course timing is all shot and you can't use it to control any real
> time processes, but it suffices to be able to program on the hoof without real
> hardware.

Is your simulator going to be running on top of Windows?

>  
> The current project will run this simulator on a dedicated processing core using
> the arinc653 scheduler (as recommended by Andrew Cooper) and making it real time
> again. 

The arinc653 scheduler is a fixed periodic timeslice scheduler, which may not be
what you want.

Can you achieve your goal with just cpu-pinning or cpu-pools and the credit or
sedf schedulers?

>  
> At the moment my development is in the initial stages of learning the Xen
> infrastructure and how to push things around. I expect to be another couple of
> weeks experimenting with ways of doing things before I decide how this should be
> done. Like for instance setting up a CPU pool with the arinc653 scheduler seems
> to crash the hypervisor.

The arinc653 scheduler currently only supports a single physical core and does
not really support CPU pools.  It would be nice if it detected these conditions
and printed an error though, instead of simply crashing...

   Nate

>>  
>> James 
> Simon.
>  
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
> 

  reply	other threads:[~2013-10-30 18:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 19:35 Mapping shared pages from Windows Simon Martin
2013-10-25 22:48 ` James Harper
2013-10-27 22:43   ` Simon Martin
2013-10-30 18:39     ` Nate Studer [this message]
2013-10-31 18:19     ` Nate Studer
2013-10-28  9:46 ` Paul Durrant

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=52715260.5@dornerworks.com \
    --to=nate.studer@dornerworks.com \
    --cc=Robert.VanVossen@dornerworks.com \
    --cc=smartin@milliways.cl \
    --cc=xen-devel@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 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).