All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nate Studer <nate.studer@dornerworks.com>
To: Simon Martin <smartin@milliways.cl>,
	Robbie VanVossen <robert.vanvossen@dornerworks.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	josh.whitehead@dornerworks.com,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: ARINC653
Date: Tue, 3 Dec 2013 10:32:29 -0500	[thread overview]
Message-ID: <529DF98D.4080508@dornerworks.com> (raw)
In-Reply-To: <emd0ee9d80-dcd1-44d3-86ac-d976b80e30bc@smartin-alien>

On 12/3/2013 7:07 AM, Simon Martin wrote:
> Hi Robbie,
>  
> Nate said that I should contact you if I was having problems with the scheduler,
> and unfortunately I have.

I am actually back, so I can field this one.

>  
> As far as I can see I have created a cpupool with 1 CPU running the arinc653
> scheduler. Here the output from xl.
>  
> root@smartin-xen <mailto:root@smartin-xen>:~# xl cpupool-list
> Name               CPUs   Sched     Active   Domain count
> Pool-0               3    credit       y          1
> pv400                1  arinc653       y          1
>  
> However the domU I load into the pv400 cpupool is never scheduled. I found a few
> mails talking about this, and it looks like I need to run a program on dom0 to
> configure the scheduler. I wrote the program and as far as I can see it should
> work, however whatever I do it fails. I tried to put a few printk statements in
> the corresponding arinc653_sched_set but I don't see any output in the xl dmesg,
> or domU log either.
>  
> I attach the code I wrote to configure the scheduler. It accepts one parameter,
> the UUID of the dom_handle I need to specify. The mail I found wasn't too clear
> so I test this using the dom0 UUID (00000000-0000-0000-0000-000000000000) and
> with the domU UUID as well. Both fail the do_sysctl call in
> xc_sched_arinc653_schedule_set (xc_arinc653.c line 51).
>  
> Can you give me some idea of what I'm doing wrong here?

Did you apply the patches I posted to the list a couple weeks ago?  I noticed
that you are calling the xc_sched_arinc653_schedule_set function without a pool
id, so I think the answer is no.

http://lists.xenproject.org/archives/html/xen-devel/2013-11/msg02549.html

Without these patches, you can only load a schedule into Pool-0.

If you just want to wait a little bit, I should be addressing Andrew's comments
soon, in order to get them into unstable.

   Nate

>  
> Regards.
>  

  reply	other threads:[~2013-12-03 15:32 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   ` Nate Studer [this message]
2013-12-03 20:19     ` ARINC653 Simon Martin
2013-12-09 20:23       ` ARINC653 Simon Martin
2013-12-09 21:28         ` ARINC653 Dario Faggioli
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=529DF98D.4080508@dornerworks.com \
    --to=nate.studer@dornerworks.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=josh.whitehead@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 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.