xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Simon Martin <smartin@milliways.cl>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	josh.whitehead@dornerworks.com,
	Nate Studer <nate.studer@dornerworks.com>,
	Robbie VanVossen <robert.vanvossen@dornerworks.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: ARINC653
Date: Mon, 9 Dec 2013 22:28:05 +0100	[thread overview]
Message-ID: <1386624485.14872.10.camel@Abyss> (raw)
In-Reply-To: <em490785cb-72ab-4c6b-973e-10da2d7b5517@smartin-alien>


[-- Attachment #1.1: Type: text/plain, Size: 2363 bytes --]

On lun, 2013-12-09 at 20:23 +0000, Simon Martin wrote:
> smartin@smartin-xen:~/projects/trio/xen/pv499$ sudo xl cpupool-list
> Name               CPUs   Sched     Active   Domain count
> Pool-0               3    credit       y          1
> pv499                1  arinc653       y          1
>
Ok, which pcpus are in each pool? In theory, it shouldn't matter, but,
you know... :-P
 
> After loading the domU into the pv499 and running the program that
> configures the arinc scheduler I get this:
>  
> smartin@smartin-xen:~/projects/trio/xen/pv499$ sudo xl list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0  2967     4     r-----
> 117.2
> pv499                                       24    32     1     r-----
> 373.0
>  
> So far so good. Now looking at the timings things are not too
> different from when I was using the credit scheduler. Running a single
> shot timer at a period of 250 µs gives me a jitter in the timer
> handler latency in the range [3.5 µs, 45 µs]. This makes it look like
> the problem in the jitter is not the scheduling but the underlying
> hypervisor. It is going off to do things on this CPU which is causing
> the deadlines not to be met.
>  
> So unless I am doing something silly it looks like I will have to go
> to RT-Xen to get better timings. For the moment I'm going to leave
> this and go on to getting more of my operating system working.
>
Well, RT-Xen is a great project, but it's mostly, if not all, about
scheduling. I mean, all they do is introducing two new schedulers (with
a couple of operational mode in each), and that's it... There is nothing
there being done for reducing latency or jitter.

I think, we'd better off (as soon as, as you said, you have more pieces
in place), trying to figure out what is causing the behavior you're
seeing and workaround/fix/amend it!

It's a busy period, with the 4.4 release, etc., but, as repeatedly said,
I'm up for helping with this, if help is needed! :-P

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

  reply	other threads:[~2013-12-09 21:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <528A34C9.7010208@dornerworks.com>
2013-12-03 12:07 ` ARINC653 Simon Martin
2013-12-03 15:32   ` ARINC653 Nate Studer
2013-12-03 20:19     ` ARINC653 Simon Martin
2013-12-09 20:23       ` ARINC653 Simon Martin
2013-12-09 21:28         ` Dario Faggioli [this message]
2013-12-09 23:08           ` ARINC653 Simon Martin
2013-12-10  9:36             ` ARINC653 Dario Faggioli
2013-12-10 11:55               ` ARINC653 Simon Martin
2013-11-28 13:07 ARINC653 Simon Martin
2013-11-28 13:55 ` ARINC653 Simon Martin

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=1386624485.14872.10.camel@Abyss \
    --to=dario.faggioli@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=josh.whitehead@dornerworks.com \
    --cc=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).