search for: pcpu1

Hi, I have found the cpu time partitioning based on cpu shares weights not very intuitive. On RHEL64, I deployed two qemu/kvm VMs VM1 with 1 vcpu and 512 cpu shares VM2 with 2 vcpus and 1024 cpu shares I pinned their vcpus to specific host pcpus: VM1 vcpu 0 to host pcpu1 VM2 vcpu 0 to host pcpu1, VM2 vcpu 1 to host pcpu2 I executed inside the VMs a simple process that consume all available cpu, eg # cat /dev/zero > /dev/null on the host, using 'top', the reported cpu usage per qemu process is : with 1 process in VM1 and 1 process on vcpu1 in VM2 VM...

...l cpu that previously received the interrupt, but currently we are doing it on the pcpu that received the maintenance interrupt. As a consequence if a vcpu is migrated to a different pcpu, the irq is going to be EOI''ed on the wrong pcpu. This covers the case where dom0 vcpu0 is running on pcpu1 for example (you can test this scenario by using xl vcpu-pin). Changes in v3: - use an int rather than a cpumask to store the EOI cpu; - adds the eoi cpu to arch_irq_desc. Changes in v2: - pass virq by value to gic_irq_eoi; - EOI the interrupt without any spin locks held and with interrupt enabl...

...l cpu that previously received the interrupt, but currently we are doing it on the pcpu that received the maintenance interrupt. As a consequence if a vcpu is migrated to a different pcpu, the irq is going to be EOI''ed on the wrong pcpu. This covers the case where dom0 vcpu0 is running on pcpu1 for example (you can test this scenario by using xl vcpu-pin). Changes in v2: - pass virq by value to gic_irq_eoi; - EOI the interrupt without any spin locks held and with interrupt enabled. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> CC: keir@xen.org --- xen/arch...