similar to: [Patch] credit: Update other parameters when setting tslice_ms

Add a xen command-line parameter, sched_credit_tslice_ms, to set the timeslice of the credit1 scheduler. Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com> diff -r 4a4882df5649 -r 782284c5b1bc xen/common/sched_credit.c --- a/xen/common/sched_credit.c Wed Aug 31 15:23:49 2011 +0100 +++ b/xen/common/sched_credit.c Thu Sep 01 16:29:50 2011 +0100 @@ -41,15 +41,9 @@ */ #define

Hi all, Since Xen 4.2.0, users can change time slice of the scheduler at runtime via xl command line, a very nice feature. However, it is not *correctly* implemented. Problem description -------------------- say you set the ''cap'' of one VM to 50 (a half core), -when setting the time slice to be *greater* than 30ms, the VM gets much *less* CPU cycles than its allocation -when

Hello, This small series deals with some weirdness in the mechanism with which the credit scheduler choses what PCPU to tickle upon a VCPU wake-up. Details are available in the changelog of the first patch. The new approach has been extensively benchmarked and proved itself either beneficial or harmless. That means it does not introduce any significant amount of overhead and/or performances

Hi, I am using Xen 4.2.3 installed on an Intel Atom with a Debian Dom0 and 3 Debian domU''s installed. I am trying to run some benchmarks using the Arinc653 scheduler. I have edited my grub options to boot with ''maxcpus=1 sched=arinc653'' options. I can boot the dom0 and verify that the scheduler is enabled. However when I xl create, the VM is created but I cannot

flight 12043 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12043/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-rhel6hvm-amd 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-rhel6hvm-intel 7 redhat-install fail REGR. vs. 12031 test-amd64-i386-xl-winxpsp3-vcpus1 7

Hi all, I have a following problem: - Remus network buffering doesn''t work. It seems to be because of no vif is reported by the function server.xend.domain on line 29 of /usr/local/lib/python2.7/dist-packages/xen/remus/vm.py (seen using pdb) : 27 if domid: 28 try: 29 self.dominfo = server.xend.domain(domid, ''all'') >

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

in _csched_cpu_pick(), as not doing so may result in the domain''s node-affinity mask (as retrieved by csched_balance_cpumask() ) and online mask (as retrieved by cpupool_scheduler_cpumask() ) having an empty intersection. Therefore, when attempting a node-affinity load balancing step and running this: ... /* Pick an online CPU from the proper affinity mask */

Hi, I was trying to add some printk in the credit scheduler to see how it works, but the printk seems not working. (it gives no output) But when I add printk in scheduler.c, it works pretty well. Does anyone know why? do I need to change some configuration file or something? Thanks very much! Best! Yours, Sisu _______________________________________________ Xen-devel mailing list

As discussed in a previous e-mail, this patch series implements yield for the credit scheduler. This allows a VM to actually yield (give up the cpu to another VM) when it wants to. This has been shown to be effective when used in the spinlock code to avoid wasting time spinning when another vcpu is not currently scheduled. _______________________________________________ Xen-devel mailing list

Hi, I have the following errors: Panic on CPU0: FATAL PAGE FAULT [error_code=0002] Faulting linear address: fbfb1100 More details in snapshots as below as I don''t have serial console cables thus unable to get full details of the errors which I will try to get one and send the full error if needed: http://choon.net/xenerrors/Image000.jpg http://choon.net/xenerrors/Image001.jpg

At least to me, using ?: instead of the (a && ...) || (!a && ...) construct is far easier to grok with a single look. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/xen/common/sched_credit.c +++ b/xen/common/sched_credit.c @@ -526,10 +526,9 @@ _csched_cpu_pick(const struct scheduler weight_cpu = cpus_weight(cpu_idlers); weight_nxt =

Signed-off-by: Vincent Hanquez <vincent.hanquez@eu.citrix.com> --- tools/ocaml/Makefile | 2 +- tools/ocaml/common.make | 2 +- tools/ocaml/libs/xl/xl.ml | 209 ++++++++++++ tools/ocaml/libs/xl/xl.mli | 209 ++++++++++++ tools/ocaml/libs/xl/xl_stubs.c | 706 ++++++++++++++++++++++++++++++++++++++++ 5 files changed, 1126 insertions(+), 2 deletions(-)

Hello, Can anyone explain the need/purpose for the following variables in the structure csched_dom found in sched_credit.c file struct csched_dom { *struct list_head active_vcpu; struct list_head active_sdom_elem; struct domain *dom;* . . Thank you _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, I''m a PhD student trying to add some load balancing code to the credit scheduler in order to fit some specific necessities. I''m trying to understand the credit scheduler code and I don''t quite get in which part of it a pcpu starts running a vcpu. I need to keep track of when a vpcu starts running in a cpu and when it stops. Any hint on that? I think that it would

Aiming at a release later in October (before Xen Summit I would hope), I''d like to cut RC1 next week. Please indicate any bug fixes that so far may have been missed in the backports already done. Jan

On Wed, Nov 23, 2011 at 2:55 PM, Dario Faggioli <raistlin@linux.it> wrote: > Hi everyone, > > This series changes how locks are dealt with while adjusting domains'' > scheduling parameters. > > I''ve done and am still doing tests for credit and credit2, and it''s > surviving to all I threw at it up to now. Unfortunately, I can''t test >

Hello, I have a lots of questions about xen. Also, i would like to explore the code in order to have a better understand of (i hope) how xen works. I have untar the source code, but i''m really lost. I''m a newbie in thatbut i want to learn how to read the code. Can someone tell me how the archive is organized ? What folders are important or not ? In fact, i would

flight 22043 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/22043/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl 9 guest-start fail REGR. vs. 22033 build-armhf 4 xen-build fail REGR. vs. 22033 test-amd64-i386-xl-qemut-winxpsp3-vcpus1