search for: extratim

Hi list, I''m using xen 3.0.0 and wonder how to obtain the 6 DOMU scheduling parameters from my DOM0 domain. Sort opposite of the sched-sedf xm sub-command Can someone help me ? Pierre _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

...xl: error: libxl.c:3619:sched_sedf_domain_set: setting domain sched sedf: Invalid argument libxl: error: libxl_create.c:710:domcreate_bootloader_done: cannot (re-)build domain: -3 Parsing config from /etc/xen/debian.guest.osstest.cfg This is due to the fact the values for period, slice, weight and extratime should be consistent among each others, and if not all are explicitly specified, someone has to make that happen. That was right the purpose of the change in question, but it was failing at achieving so. This commit fixes things by forcing unspecified parameters to sensible values, depending on t...

...PyObject *kwds) ... - return Py_BuildValue("{s:i,s:L,s:L,s:L,s:i}", - "domain", domid, - "period", period, - "slice", slice, - "latency", latency, - "extratime", extratime); + return Py_BuildValue("{s:i,s:L,s:L,s:L,s:i,s:i}", + "domain", domid, + "period", period, + "slice", slice, + "latency", latency, + &q...

...wish to change -Adds additional testing of sched-sedf via new xm-test testcases. With this patch applied, test 02_sedf_period_lower_neg.py exposes a bug[4]. I''ll follow up this email with a patch for the bug. 1. root@bebop:~ # xm sched-sedf Name ID Period Slice Latency ExtraTime Weight Domain-0 0 20000000 15000000 0 1 0 2. root@bebop:~ # xm sched-sedf 0 --extratime=0 root@bebop:~ # xm sched-sedf Name ID Period Slice Latency ExtraTime Weight Domain-0 0 20000000 15000000 0 0 0 3. root@bebop:~ # xm h...

...eeping*/ + /* Bookkeeping */ s_time_t deadl_abs; s_time_t sched_start_abs; s_time_t cputime; - /* times the domain un-/blocked */ + /* Times the domain un-/blocked */ s_time_t block_abs; s_time_t unblock_abs; - /*scores for {util, block penalty}-weighted extratime distribution*/ + /* Scores for {util, block penalty}-weighted extratime distribution */ int score[2]; s_time_t short_block_lost_tot; - /*Statistics*/ + /* Statistics */ s_time_t extra_time_tot; #ifdef SEDF_STATS @@ -158,18 +151,16 @@ static inline void extraq_del(...

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

...I found an easy setup that works for me: I set the scheduling parameters for all domains via "xm sched-sedf <domID> 0 0 0 1 1" or something similar corresponding to example "4 domains with weights 2:3:4:2" from the sedf_scheduler_mini-HOWTO.txt with an additional 1 as the extratime parameter if you want to allow a domain to allocate more CPU time if other domains are idle. With these two issues fixed the system runs just great. As a total xen noob I don''t dare touch the wiki, but if someone more experienced could verify that these issues are valid, adding some hi...

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com> -- 1.7.10.4

...eduler_op.sched_id) { + case XEN_SCHEDULER_SEDF: + PRE_XEN_DOMCTL_READ(scheduler_op, u.sedf.period); + PRE_XEN_DOMCTL_READ(scheduler_op, u.sedf.slice); + PRE_XEN_DOMCTL_READ(scheduler_op, u.sedf.latency); + PRE_XEN_DOMCTL_READ(scheduler_op, u.sedf.extratime); + PRE_XEN_DOMCTL_READ(scheduler_op, u.sedf.weight); + break; + case XEN_SCHEDULER_CREDIT: + PRE_XEN_DOMCTL_READ(scheduler_op, u.credit.weight); + PRE_XEN_DOMCTL_READ(scheduler_op, u.credit.cap); + break; + case XEN_SCHEDULER_...

...RENCE) -libxl_file_reference = Builtin("file_reference", dispose_fn="libxl_file_reference_dispose", passby=PASS_BY_REFERENCE) - libxl_hwcap = Builtin("hwcap", passby=PASS_BY_REFERENCE) # @@ -235,11 +233,6 @@ libxl_sched_params = Struct("sched_param ("extratime", integer), ], dir=DIR_IN) -# Instances of libxl_file_reference contained in this struct which -# have been mapped (with libxl_file_reference_map) will be unmapped -# by libxl_domain_build/restore. If either of these are never called -# then the user is responsible for calling -# li...

...uot;:null,"device_model_ssidref":0,"extra":[],"extra_pv":[],"extra_hvm":[],"sched_params":{"weight":0,"cap":0,"tslice_ms":0,"ratelimit_us":0,"period":0,"slice":0,"latency":0,"extratime":0},"u":{"kernel":"/boot/vmlinuz-3.2.0-24-generic-pae","slack_memkb":-1,"bootloader":null,"bootloader_args":[],"cmdline":"root=/dev/xvda2 ro ","ramdisk":"/boot/initrd.img-3.2.0-24-generic-pae",...

...1 +struct xen_domctl_scheduler_op { + uint32_t sched_id; /* XEN_SCHEDULER_* */ + uint32_t cmd; /* XEN_DOMCTL_SCHEDOP_* */ + union { + struct xen_domctl_sched_sedf { + uint64_t period; + uint64_t slice; + uint64_t latency; + uint32_t extratime; + uint32_t weight; + } sedf; + struct xen_domctl_sched_credit { + uint16_t weight; + uint16_t cap; + } credit; + } u; +}; +typedef struct xen_domctl_scheduler_op xen_domctl_scheduler_op_t; +DEFINE_XEN_GUEST_HANDLE(xen_domctl_scheduler_op_t)...