search for: credit2

Hi, everyone, I''m curious about what are the differences between credit2 and credit1 of xen''s scheduler? And is credit2 will release in xen-4.1? Are there some one can tell me some details about them? or just tell me where can I find some reference about them? Thanks in advance :) -- - Luit @ Parallel Processing Institute, Fudan University ________________...

In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> credit2: Fix erronous ASSERT In order to avoid high-frequency cpu migration, vcpus may in fact be scheduled slightly out-of-order. Account for this situation properly. v2: - Update comment - <= 0 Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> --- xen/common/sched_credit2.c | 4...

Address some credit2 issues. This patch series, along with the recent changes to the cpupools interface, should address some of the strange credit2 instability. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, I observed that a configuration where dom0 vcpus were pinned to a set of pcpus in the host using dom0_vcpus_pin and the guests were prevented from running on the dom0 pcpus (here called "exclusively-pinned dom0 vcpus", or xpin) caused the general performance of the guests in a host with around 24 pcpus or more to increase during bootstorms and high density of guests, even

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

Hi, I''ve installed xen-unstable 4.2 from actual git (last commit was 4dc7dbef5400f0608321d579aebb57f933e8f707). When I start a domU with xm all is fine include the cpu_weight I configured in my domU config. When I start the domU with xl then all my domU have the default cpu_weight of 256 instead of the configured one. Was the name of cpu_weight being changed for xl command ? My domU

...install fail never pass test-amd64-i386-rhel6hvm-intel 7 redhat-install fail never pass test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass test-amd64-i386-win 16 leak-check/check fail never pass test-amd64-i386-xl-credit2 14 guest-localmigrate/x10 fail blocked in 5691 test-amd64-i386-xl-multivcpu 15 guest-stop fail never pass test-amd64-i386-xl-win-vcpus1 7 windows-install fail never pass test-amd64-i386-xl 15 guest-stop fail never pass test-a...

...hvm-amd 1 xen-build-check(1) blocked n/a test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-win 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-win-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-xl 1 xen-build-check(1) blocked n/a test-amd64-xcpkern-i386-p...

flight 5503 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/5503/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-amd64-i386-xl-credit2 14 guest-localmigrate/x10 fail pass in 5502 test-amd64-xcpkern-i386-xl 14 guest-localmigrate/x10 fail pass in 5502 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-win 16 leak-check/...

flight 6412 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/6412/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-xcpkern-i386-xl-credit2 11 guest-localmigrate fail REGR. vs. 6379 Tests which did not succeed, but are not blocking, including regressions (tests previously passed) regarded as allowable: test-amd64-amd64-win 16 leak-check/check fail never pass test-amd64-amd64-xl-win 13 guest-stop...

...hvm-amd 1 xen-build-check(1) blocked n/a test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-win 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-win-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-xl 1 xen-build-check(1) blocked n/a test-amd64-xcpkern-i386-p...

Hey George, I was wondering if you could explain in simple terms how the scheduler would handle per-physical CPU when there are say 16 guests (each guest is using one VCPU), 32 physical CPUs and dom0 is not restricted to any CPUs. Would the scheduler per physical CPU schedule: guest, dom0, guest, dom0, and so on; or would it be more random? (I assume that both guest and dom0 would do a hypercall

...d64-xcpkern-i386-xl pass test-i386-xcpkern-i386-xl pass test-amd64-i386-rhel6hvm-amd fail test-amd64-xcpkern-i386-rhel6hvm-amd fail test-amd64-i386-xl-credit2 pass test-amd64-xcpkern-i386-xl-credit2 pass test-amd64-i386-rhel6hvm-intel fail test-amd64-xcpkern-i386-rhel6hvm-intel fail test-amd64-i386-xl-multivcpu...

...3776 linux-mingo-tip-master real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13776/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xend-winxpsp3 5 xen-boot fail REGR. vs. 12678 test-amd64-i386-xl-credit2 5 xen-boot fail REGR. vs. 12678 test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 12678 test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 12678 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 5...

...http://www.chiark.greenend.org.uk/~xensrcts/logs/7124/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-i386-pair 16 guest-start fail REGR. vs. 7062 test-amd64-i386-pv 9 guest-start fail REGR. vs. 7062 test-amd64-i386-xl-credit2 9 guest-start fail REGR. vs. 7062 test-amd64-i386-xl-multivcpu 9 guest-start fail REGR. vs. 7062 test-amd64-i386-xl 9 guest-start fail REGR. vs. 7062 test-i386-i386-pair 16 guest-start fail REGR. vs. 7062 test-i...

flight 10458 xen-4.1-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10458/ Failures and problems with tests :-( Tests which did not succeed and are blocking: test-amd64-i386-xl-credit2 3 host-install(3) broken test-amd64-amd64-xl-sedf 3 host-install(3) broken test-amd64-amd64-xl-winxpsp3 3 host-install(3) broken test-amd64-amd64-pv 3 host-install(3) broken test-amd64-i386-win-vcpus1 3 host-install(3)...

Hi all (and Mr. Dunlap in particular), I have a question about the credit (and ultimately credit2) scheduler that I hope you can help me with. I have read the white paper "Scheduler development update" and as much material on the credit scheduler as I can find, but I am still not completely clear on how I should think about the cap. Example scenario: Server hardware: 2 soc...

...d64-xcpkern-i386-xl pass test-i386-xcpkern-i386-xl pass test-amd64-i386-rhel6hvm-amd fail test-amd64-xcpkern-i386-rhel6hvm-amd fail test-amd64-i386-xl-credit2 pass test-amd64-xcpkern-i386-xl-credit2 pass test-amd64-i386-rhel6hvm-intel fail test-amd64-xcpkern-i386-rhel6hvm-intel fail test-amd64-i386-xl-multivcpu...

...an-fixup fail never pass test-amd64-i386-xl-multivcpu 15 guest-stop fail never pass test-i386-i386-xl 15 guest-stop fail never pass test-amd64-i386-xl 15 guest-stop fail never pass test-amd64-i386-xl-credit2 5 xen-boot fail like 8149 test-amd64-i386-rhel6hvm-intel 7 redhat-install fail never pass test-amd64-i386-rhel6hvm-amd 7 redhat-install fail never pass test-amd64-i386-win-vcpus1 16 leak-check/check fail never pass test-a...

...hvm-amd 1 xen-build-check(1) blocked n/a test-amd64-i386-rhel6hvm-intel 1 xen-build-check(1) blocked n/a test-amd64-i386-win-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-win 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-credit2 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-multivcpu 1 xen-build-check(1) blocked n/a test-amd64-i386-xl-win-vcpus1 1 xen-build-check(1) blocked n/a test-amd64-i386-xl 1 xen-build-check(1) blocked n/a test-amd64-xcpkern-i386-p...