On Mon, 24 Oct 2022, Michal Orzel wrote:
> Replying to all,
>
> On 21/10/2022 21:36, Stefano Stabellini wrote:
> >
> >
> > On Fri, 21 Oct 2022, Andrew Cooper wrote:
> >> On 21/10/2022 17:53, Michal Orzel wrote:
> >>> Null scheduler is not enabled on non-debug Xen builds so the current
> >>> test
On 24/10/2022 07:29, Jan Beulich wrote:
> On 21.10.2022 19:21, Andrew Cooper wrote:
>> On 21/10/2022 17:53, Michal Orzel wrote:
>>> Null scheduler is not enabled on non-debug Xen builds so the current
>>> test can lead to a failure on such jobs. We still want to test that we
>>> can assign the cpup
Replying to all,
On 21/10/2022 21:36, Stefano Stabellini wrote:
>
>
> On Fri, 21 Oct 2022, Andrew Cooper wrote:
>> On 21/10/2022 17:53, Michal Orzel wrote:
>>> Null scheduler is not enabled on non-debug Xen builds so the current
>>> test can lead to a failure on such jobs. We still want to test
On 21.10.2022 19:21, Andrew Cooper wrote:
> On 21/10/2022 17:53, Michal Orzel wrote:
>> Null scheduler is not enabled on non-debug Xen builds so the current
>> test can lead to a failure on such jobs. We still want to test that we
>> can assign the cpupool to a domU with a different scheduler than
Hi Stefano,
On 21/10/2022 20:36, Stefano Stabellini wrote:
For the NULL scheduler, it is clearly important to many users so it
would be valuable to move it to "supported, non security supported" and
enabling it by default in the build. I don't recall if we still have any
known outstanding issues
On Fri, 21 Oct 2022, Andrew Cooper wrote:
> On 21/10/2022 17:53, Michal Orzel wrote:
> > Null scheduler is not enabled on non-debug Xen builds so the current
> > test can lead to a failure on such jobs. We still want to test that we
> > can assign the cpupool to a domU with a different scheduler th
On 21/10/2022 17:53, Michal Orzel wrote:
> Null scheduler is not enabled on non-debug Xen builds so the current
> test can lead to a failure on such jobs. We still want to test that we
> can assign the cpupool to a domU with a different scheduler than default
> one (credit2). Switch to credit as it
Null scheduler is not enabled on non-debug Xen builds so the current
test can lead to a failure on such jobs. We still want to test that we
can assign the cpupool to a domU with a different scheduler than default
one (credit2). Switch to credit as it is enabled by default.
Fixes: 36e3f4158778 ("au
