Messages in this thread | | | Subject | Re: [PATCH 4/4] nohz: Set isolcpus when nohz_full is set | From | Mike Galbraith <> | Date | Tue, 19 May 2015 04:30:32 +0200 |
| |
On Mon, 2015-05-18 at 10:52 -0400, Rik van Riel wrote:
> For real time KVM, it is desirable to run the VCPU threads on > isolated CPUs as real time tasks. > > Meanwhile, the emulator threads can run as normal tasks anywhere > on the system. > > This means the /machine cpuset, which all guests live under, > needs to contain all the system's CPUs, both isolated and > non-isolated, otherwise it will be unable to have the VCPU > threads on isolated CPUs and the emulator threads on other > CPUs.
Ok, I know next to nothing about virtualization only because I failed at maintaining the desired absolute zero, but...
Why do you use isolcpus for this? This KVM setup sounds very similar to what I do for real realtime. I use a shield script to set up an exclusive isolated set and a system set and move the mundane world into the system set. Inject realtime proggy into its exclusive home, it creates/pins worker bees, done. Why the cpuset isolcpus hybrid?
When you say emulator threads can run anywhere, it sounds like that includes the isolated set, but even so, nothing prevents injecting whatever (the kernel permits) into whichever set.
-Mike
| |