| /xen/tools/ocaml/test/ |
| A D | list_domains.ml | 8 and blocked = bool_as_char dominfo.Xenlight.Dominfo.blocked 'b'
14 printf "Dom %d: %c%c%c%c%c %LdKB\n" id running blocked paused shutdown dying memory
|
| /xen/tools/tests/depriv/ |
| A D | depriv-fd-checker.c | 129 static void blocked(const char *what) { in blocked() function
156 blocked("xc_get_online_cpus"); in test_privcmd()
199 blocked("xengnttab_grant_copy"); in test_gntdev()
272 blocked("xenevtchn_notify"); in test_evtchn()
|
| /xen/docs/misc/ |
| A D | vtd-pi.txt | 132 5. Introduce a new global vector which is used for waking up the blocked vCPU.
135 8. How to wakeup blocked vCPU when an interrupt is posted for it (wakeup notification handler).
217 - Introduce a new global vector which is used to wake up the blocked vCPU.
231 wakeup the blocked vCPU, please refer to later section in this design for
256 2. When vCPU is blocked
276 2. vCPU0 is blocked and vCPU1 is currently running on pCPU0
283 another global vector, naming 'pi_wakeup_vector' to wake up the blocked vCPU.
289 can do something in it, such as wakeup the blocked vCPU.
291 Here are what we do for the blocked vCPU:
292 1. Define a per-cpu list 'pi_blocked_vcpu', which stored the blocked
[all …]
|
| A D | xenmon.txt | 41 This is how much time the domain spent blocked (or sleeping); Put another way,
45 o Total time blocked over the measurement interval
|
| A D | xen-command-line.pandoc | 2248 stop_machine context. In NMI handler, even NMIs are blocked, which is
|
| /xen/xen/common/ |
| A D | vm_event.c | 126 if ( avail_req == 0 || ved->blocked == 0 ) in vm_event_wake_blocked()
138 if ( !ved->blocked || avail_req == 0 ) in vm_event_wake_blocked()
145 ved->blocked--; in vm_event_wake_blocked()
204 ved->blocked--; in vm_event_disable()
243 ved->blocked++; in vm_event_mark_and_pause()
|
| A D | domctl.c | 725 op->u.getvcpuinfo.blocked = !!(v->pause_flags & VPF_blocked); in do_domctl()
|
| /xen/xen/include/xen/ |
| A D | vm_event.h | 47 unsigned int blocked; member
|
| /xen/xen/arch/x86/cpu/ |
| A D | vpmu_intel.c | 616 bool_t blocked = 0; in core2_vpmu_do_wrmsr() local
628 blocked = 1; in core2_vpmu_do_wrmsr()
640 blocked = 0; in core2_vpmu_do_wrmsr()
654 blocked = 0; in core2_vpmu_do_wrmsr()
659 if ( blocked ) in core2_vpmu_do_wrmsr()
|
| /xen/tools/ocaml/libs/xc/ |
| A D | xenctrl.ml | 25 blocked: bool; RecordField
90 blocked : bool; RecordField
|
| A D | xenctrl.mli | 20 blocked : bool; RecordField
81 blocked : bool; RecordField
|
| A D | xenctrl_stubs.c | 483 Store_field(result, 1, Val_bool(info.blocked)); in stub_xc_vcpu_getinfo()
|
| /xen/tools/xl/ |
| A D | xl_vcpu.c | 44 vcpuinfo->blocked ? 'b' : '-'); in print_vcpuinfo()
|
| A D | xl_info.c | 405 info[i].blocked ? 'b' : '-', in list_domains()
|
| /xen/xen/ |
| A D | Kconfig.debug | 59 Lock profiling allows you to see how often locks are taken and blocked.
|
| /xen/xen/include/public/ |
| A D | domctl.h | 285 uint8_t blocked; /* blocked waiting for an event? */ member
|
| /xen/tools/libxl/ |
| A D | libxl_types.idl | 337 ("blocked", bool),
1020 ("blocked", bool),
|
| A D | libxl_domain.c | 291 xlinfo->blocked = !!(xcinfo->flags&XEN_DOMINF_blocked); in libxl__xcinfo2xlinfo()
1702 ptr->blocked = !!vcpuinfo.blocked; in libxl_list_vcpu()
|
| /xen/tools/xenmon/ |
| A D | xenmon.py | 413 if options.blocked:
|
| /xen/tools/python/xen/lowlevel/xc/ |
| A D | xc.c | 376 "blocked", info[i].blocked, in pyxc_domain_getinfo()
445 "blocked", info.blocked, in pyxc_vcpu_getinfo()
|
| /xen/tools/golang/xenlight/ |
| A D | helpers.gen.go | 314 x.Blocked = bool(xc.blocked)
346 xc.blocked = C.bool(x.Blocked)
3281 x.Blocked = bool(xc.blocked)
3301 xc.blocked = C.bool(x.Blocked)
|
| /xen/tools/libxc/include/ |
| A D | xenctrl.h | 454 paused:1, blocked:1, running:1, member
|
| /xen/tools/libxc/ |
| A D | xc_domain.c | 374 info->blocked = !!(domctl.u.getdomaininfo.flags&XEN_DOMINF_blocked); in xc_domain_getinfo()
|
| /xen/docs/man/ |
| A D | xl.1.pod.in | 352 =item B<b - blocked>
354 The domain is blocked, and not running or runnable. This can be because the
|