Re: VCPUOP_set_periodic_timer

[Andrew Cooper <andrew.cooper3@citrix.com>]

On 15/11/13 12:46, Nate Studer wrote:
> 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.

Absolutely post the patches.  The worst that can happen is that they are
labelled as differed, but at least they are available for people to use.

It is George's call, but if they are small and fairly contained then
they might be fine to go in.

~Andrew