Searched refs:thread (Results 1 – 7 of 7) sorted by relevance
| /xen-4.10.0-shim-comet/tools/memshr/ |
| A D | bidir-daemon.c | 94 pthread_t thread; in bidir_daemon_launch() local
96 pthread_create(&thread, NULL, bidir_daemon, NULL); in bidir_daemon_launch()
|
| /xen-4.10.0-shim-comet/unmodified_drivers/linux-2.6/platform-pci/ |
| A D | panic-handler.c | 16 current->thread.ksp = (__u64)info->sw - 16; in xen_panic_hypercall()
|
| /xen-4.10.0-shim-comet/tools/debugger/gdbsx/ |
| A D | README | 42 Thus, gdb>info threads : will show all vcpus. Then, switch thread
43 to get to another vcpu, etc... Remember, gdb has it's own [thread]
|
| /xen-4.10.0-shim-comet/docs/misc/ |
| A D | netif-staging-grants.pandoc | 222 [*Linux-specific*: It contains a thread that is woken for this purpose. And
316 (protected by a lock) whereas a separate thread takes it from that queue and
317 process the actual like the steps below. This thread has the purpose of
|
| /xen-4.10.0-shim-comet/tools/ocaml/xenstored/ |
| A D | domains.ml | 25 (* N.B. the Queue module is not thread-safe but oxenstored is single-threaded. *)
|
| /xen-4.10.0-shim-comet/docs/features/ |
| A D | feature-levelling.pandoc | 182 Xen currently has no concept of per-{socket,core,thread} CPUID information.
|
| A D | intel_psr_cat_cdp.pandoc | 219 When context switch happens, the COS of VCPU is written to per-thread MSR
|
Completed in 6 milliseconds