search for: sched_sedf

...atch, for testing convenience. Hey Dario, sorry for the long delay in responding. Overall the patch series looks good to me. The only issue I see is that it looks like you introduce a regression between patch 2 and 3 -- that is, if you apply patches 1 and 2, but not 3, then the lock you grab in sched_sedf.c:sedf_adjust() won''t protect against concurrent accesses from other vcpus; nor will it correctly handle updates to the per-vcpu EDOM_INFO() variables. Regressions in mid-patch series are bad because it can mess up bisection. I think a better way of breaking it down would be: * Add sched...

When using sedf scheduler in a cpupool the system might panic when setting sedf scheduling parameters for a domain. Signed-off-by: juergen.gross@ts.fujitsu.com 1 file changed, 4 insertions(+) xen/common/sched_sedf.c | 4 ++++ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

sched_sedf.c used o have its own mechanism for producing tracing-alike kind of information (domain block, wakeup, etc.). Nowadays, with an even not so high number of pCPUs/vCPUs, just trying to enable this makes the serial console completely unusable, produces tons of very hard to parse and interpreet logging...

I''m working on a new hypercall, do_confer, which allows the directed yielding of a vcpu to another vcpu. It is mainly used when a vcpu fails to acquire a spinlock, yielding to the lock holder instead of spinning. I ported the ppc64 spinlock implementation for the i386 linux portion. In implementing the hypercall, I''ve been trying to figure out how to get the scheduler

...-w, --weight mutually exclusive with period/slice and specifies another way of setting a domain''s cpu period/slice. 4. (XEN) Assertion ''curinf->deadl_abs > now'' failed, line 582, file sched_sedf.c (XEN) BUG at sched_sedf.c:582 (XEN) (file=extable.c, line=77) Pre-exception: ff119c79 -> 00000000 (XEN) ----[ Xen-3.0.0 Not tainted ]---- (XEN) CPU: 1 (XEN) EIP: e008:[<ff119c79>] update_queues+0x38e/0x41e (XEN) EFLAGS: 00010092 CONTEXT: hypervisor (XEN) eax: ff1b02b8 ebx: 0...

Hi, I just added 32GB memory in my system and wanted Xen to see that memory, so enabled PAE in xen0 and XenU. I did a make menuconfig in xen0 and xenU, then did a make in xen-unstable and a make install. Whilebooting this kernel, I get the above error PAE mode mismatch. I looked under xen/include/asm-x86/processor.h has #define X86_CR4_PAE defined and so does cpufeature.h have this defined.

Hi, I have successfully installed Xen unstable binary on SuSE 9.3. I am trying to do a source install and I got the following error. Will be glad for any help or guidance. In file included from include/asm-xen/asm/processor.h:18, from include/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/spinlock.h:12, from include/linux/capability.h:45, from

...xen/common/libelf/libelf-dominfo.c | 6 + xen/common/libelf/libelf-loader.c | 21 +- xen/common/memory.c | 4 +- xen/common/sched_credit.c | 7 +- xen/common/sched_credit2.c | 11 +- xen/common/sched_sedf.c | 30 +- xen/common/shutdown.c | 4 + xen/common/spinlock.c | 1 + xen/common/timer.c | 7 +- xen/common/tmem.c | 3 +- xen/common/tmem_xen.c...