From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: Porting an OS to Xen Date: Mon, 14 Oct 2013 17:37:43 +0100 Message-ID: <525C1DD7.7050105@citrix.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4481462987722499127==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Simon Martin Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org --===============4481462987722499127== Content-Type: multipart/alternative; boundary="------------020304080801020706090708" --------------020304080801020706090708 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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 --------------020304080801020706090708 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: 8bit

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
--------------020304080801020706090708-- --===============4481462987722499127== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============4481462987722499127==--