From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nate Studer Subject: Re: VCPUOP_set_periodic_timer Date: Fri, 15 Nov 2013 07:46:10 -0500 Message-ID: <52861792.8090905@dornerworks.com> References: <528610BE.2080802@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <528610BE.2080802@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Andrew Cooper , Simon Martin Cc: George Dunlap , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 11/15/2013 7:17 AM, Andrew Cooper wrote: > > The cpupool issue with the arinc653 scheduler is now fixed (or at least believed > to be) in xen-unstable. The crashes are fixed in unstable, but pools still do not work in xen-unstable unless the system is booted with the arinc653 scheduler, the dom0_max_vcpus parameter is set to 1, and cpu0 is never removed from Pool-0. I have pools working locally without these restrictions, but I was unable to get a patchset around before the feature freeze was declared, so I believe it is too late to try and get it into unstable. (George, correct me if I am wrong.) However, I am more than happy to provide Simon with my patches to get arinc653 cpu-pools completely working with the understanding that they may change before they make it into xen-unstable. Also, the arinc653 scheduler currently only supports a scheduling resolution of 1ms, but it is a trivial task to change it some other resolution. > > ~Andrew > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >