From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Simon Martin <smartin@milliways.cl>
Cc: xen-devel@lists.xen.org
Subject: Re: Porting an OS to Xen
Date: Mon, 14 Oct 2013 17:37:43 +0100 [thread overview]
Message-ID: <525C1DD7.7050105@citrix.com> (raw)
In-Reply-To: <em8e0ab2b8-7b9f-489a-8c94-42105ad47619@smartin-alien>
[-- Attachment #1.1: Type: text/plain, Size: 712 bytes --]
On 14/10/13 17:22, Simon Martin wrote:
>>
>> One final thing which come to mind given your request which you might
>> or might not be aware of: Xen has "arinc653", a maintained realtime
>> scheduler which will likely be more appropriate to your requirements
>> than the default "credit" scheduler.
> For simplicity's sake at the moment I propose to run my VM as the
> only VM on a vcpu. My assumption is that this way there will be no
> scheduling. Is this assumption correct?
Your best option would be to create a cpupool for the individual cpu you
want your VM to be running on. This way you can schedule that cpu using
arinc653 independently of dom0 and domU being scheduled using regular
credit.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2176 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2013-10-14 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 20:28 Porting an OS to Xen Simon Martin
2013-10-13 23:07 ` Andrew Cooper
2013-10-14 16:22 ` Simon Martin
2013-10-14 16:31 ` Ian Campbell
2013-10-14 16:37 ` Andrew Cooper [this message]
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=525C1DD7.7050105@citrix.com \
--to=andrew.cooper3@citrix.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).