Re: Domain-0 CPU pinning - is it still a best practice?

[Pierre-Philipp Braun <pbraun@xxxxxxxxxxxx>]

> cpus = "all,^0,^1"
I rather share all CPUs and let the scheduler prioritize dom0 as such 
(default weight is 256):
xl sched-credit2 --domain=0 --weight=512

The only drawback is that I need to be careful on what I do on the host, 
to let some juice available for the guests.  The good thing about it is 
that the dom0 also shares all cores, I guess)
Sorry it's not a definitive answer, as I did not compare and 
stress-bench this against an old-school pinning setup.
--
Pierre-Philipp Braun
SMTP Health Campaign: enforce STARTTLS and verify MX certificates
<https://nethence.com/smtp/>