Displaying 5 results from an estimated 5 matches for "do_schedule".
Did you mean:
io_schedule
2005 Feb 23
19
Calculating real cpu usage of Xen domains correctly!
Hi all,
With the new vm-tools we are trying to get top like capabilities going
correctly. Currently we have a program vm-list that has some of this
capability but is dependent on the cpu time given by libxc calls
(xc_get_dom_info & xc_domain_get_cpu_usage). These two functions give
you how much time (in nanoseconds, why is this not documented) the
domain has been actively used. Approaches:
2005 May 17
8
scheduler independent forced vcpu selection
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
2010 Aug 19
1
Credit Scheduler code question
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
2010 Aug 09
2
[PATCH 0 of 2] Scheduler: Implement yield for credit scheduler
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
2011 Dec 20
0
sedf: remove useless tracing printk and harmonize comments style.
...eral: determine which domain to run next*/
+ * Reasons for calling this function are:
+ * -timeslice for the current period used up
+ * -domain on waitqueue has started it''s period
+ * -and various others ;) in general: determine which domain to run next
+ */
static struct task_slice sedf_do_schedule(
const struct scheduler *ops, s_time_t now, bool_t tasklet_work_scheduled)
{
@@ -789,13 +731,14 @@ static struct task_slice sedf_do_schedul
struct sedf_vcpu_info *runinf, *waitinf;
struct task_slice ret;
- /*idle tasks don''t need any of the following stuf*/
+ /...