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: Tue, 10 Dec 2013 10:36:03 +0100 [thread overview]
Message-ID: <1386668163.5488.15.camel@Solace> (raw)
In-Reply-To: <em5e5a2a52-6b50-4967-a499-c79a50ece0a4@smartin-alien>
[-- Attachment #1.1: Type: text/plain, Size: 1498 bytes --]
On lun, 2013-12-09 at 23:08 +0000, Simon Martin wrote:
> Thanks Dario,
>
> > > 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
> >
> Pool-0 has pcpu 1, 2 and 3
> pv499 has pcpu 0.
>
Can you try the opposite? I mean, something like having the 1 pCPU only
pool when you run your domU *not* including pCPU #0?
I can't point the finger to anything specific right now, but, you now,
pCPU #0 is the first being brought up, etc.
Probably, as scheduling does not matter much to you, you can even just
use vCPU affinities/pinning, like having Dom0 pinned to pCPUs 0-2, and
your DomU to pCPU 3.
> > 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
> Thanks. This is something that is going to take a while to get sorted
> so I'll definitely be plugging until way after 4.4 is done
> and dusted.
>
Well, in that case I'm sure I'll be able to help a bit. :-)
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-12-10 9:36 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 ` ARINC653 Dario Faggioli
2013-12-09 23:08 ` ARINC653 Simon Martin
2013-12-10 9:36 ` Dario Faggioli [this message]
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=1386668163.5488.15.camel@Solace \
--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 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.