Usage method and parameter description
cpu $option
Possible options and explanations:
partition name
It is used to specify the partition location where the vCPU thread runs (whether it runs in adaptive partitioning). If no partition option is specified, vCPU threads will run in the partition where the qvm process was started
runmask cpu_number{,cpu_number}
Configure whether virtual CPUs allow floating (floating), and the range of floating physical CPUs. To give a few examples:
cpu sched 10 runmask 7: This configuration virtualizes a vcpu, and the task of this vcpu will only run on the physical cpu7
cpu sched 10 runmask 1,2,3: This configuration virtualizes a vcpu, and the task of this vcpu can run on physical cpu 1/2/3. Normally, vcpu will give priority to the core with the lowest loading among the three physical cpus when assigning tasks.
sched priority[r | f | o ]
sched high_priority,low_priority,max_replacements,replacement_period,initial_budget s
Set the scheduling priority and scheduling algorithm of the vCPU. The scheduling algorithm can be round-robin (r), first-in-first-out (FIFO, f) or sporadic (s). o The (other) scheduling algorithm is reserved for future use; the default vCPU configuration uses round-robin scheduling for vCPUs. QNX suggests that most clients respond most positively to this scheduling algorithm. It allows clients with their own internal scheduling policies to operate efficiently.
The following example shows a case of 7 virtual vcpus (each row represents a vcpu), example:
cpu sched 10 runmask 6,5,4
cpu sched 10 runmask 5,4,6
cpu sched 10 runmask 4,6,5
cpu sched 10 runmask 1,2,3
cpu sched 10 runmask 1,2,3
cpu sched 10 runmask 1,2,3
cpu sched 10 runmask 7
reference page
http://www.qnx.com/developers/docs/7.0.0/#com.qnx.doc.hypervisor.user/topic/vm/cpu.html