>>> On 03.03.15 at 11:51, <jbeul...@suse.com> wrote:
> That would then leave introducing a "relaxed (or "strict",
> depending on what we'd like to be the default) mode in the patch
> here, controlling whether ->cpu_hard_affinity gets overridden
> (and we'd always override ->cpu_soft_affinity).

Having implemented this "relaxed" addition (patch to be posted after
a few more tests), I find that with Dom0 being restricted to half of
the nodes of the test system, soft affinity set to that set, and hard
affinity left set to "all", many Dom0 vCPU-s nevertheless run on the
CPUs not in its soft affinity (and there's no other load on the system).
Is there a bug in that (credit) scheduler logic somewhere?

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to