Searched refs:scheduled (Results 1 – 6 of 6) sorted by relevance
/xen-4.10.0-shim-comet/xen/arch/x86/hvm/ |
A D | vpt.c | 163 missed_ticks = now - pt->scheduled; in pt_process_missed_ticks() 172 pt->scheduled += missed_ticks * pt->period; in pt_process_missed_ticks() 226 set_timer(&pt->timer, pt->scheduled); in pt_restore_timer() 242 pt->scheduled += pt->period; in pt_timer_fn() 378 set_timer(&pt->timer, pt->scheduled); in pt_intr_post() 387 set_timer(&pt->timer, pt->scheduled); in pt_intr_post() 445 pt->scheduled = NOW() + delta; in create_periodic_time() 451 pt->scheduled = align_timer(pt->scheduled, pt->period); in create_periodic_time() 461 pt->scheduled += delta >> 1; in create_periodic_time() 472 set_timer(&pt->timer, pt->scheduled); in create_periodic_time()
|
/xen-4.10.0-shim-comet/xen/include/asm-x86/hvm/ |
A D | vpt.h | 52 s_time_t scheduled; /* scheduled timer interrupt */ member
|
/xen-4.10.0-shim-comet/docs/man/ |
A D | xl-numa-placement.pod.7 | 104 In this case, the vCPU is always scheduled on one of the pCPUs to which 119 pCPUs. In this case, the vCPU is always scheduled on one of the pCPUs 143 should be created and scheduled on, directly in its config file. This
|
A D | xl.pod.1.in | 1121 While scheduled, a VCPU burns its budget.
|
/xen-4.10.0-shim-comet/docs/misc/ |
A D | xenmon.txt | 18 o The number of times that a domain was scheduled to run (ie, dispatched) over
|
A D | xen-command-line.markdown | 1567 amount of time that a vcpu can be scheduled for before preempting it,
|
Completed in 11 milliseconds